WebSVN – DevTools – Diff – /core_devl/trunk/TOOLS/jats_sandbox.pl

 use JatsError;
 use JatsSystem;
 use FileUtils;
 use JatsBuildFiles;
 use JatsVersionUtils;
-use File::Path qw(rmtree);
 use Pod::Usage;                             # required for help support
 use Getopt::Long qw(:config require_order); # Stop on non-option
 my $VERSION = "1.0.0";                      # Update this
 # Description     : Delete a sandbox
 #                   Its up to the user the delete the components in the sandbox
+#
 # Inputs          : None
+#
 # Returns         :
+#
 sub delete_sandbox
+{
     GetOptions (
                 "help:+"        => \$opt_help,
+    {
         Warning("No sandbox found to delete");
+    }
     else
+    {
-        my $sdir = "$GBE_SANDBOX/sandbox_dpkg_archive";
-        rmtree($sdir,0,0);
         Error ("Sandbox directory not completly removed")
-            if ( -e $sdir );
+            if RmDirTree( "$GBE_SANDBOX/sandbox_dpkg_archive" );
         Message("Sandbox information deleted",
                 "Sandbox components must be manually deleted");
+    }
     exit 0;
                 "manual:3"      => \$opt_help,
                 "verbose:+"     => \$opt_verbose,
                 ) || Error ("Invalid command line" );
     SubCommandHelp( $opt_help, "Sandbox Information") if ($opt_help || $#ARGV >=0 );
+    #
     #   Determine Sandbox information
     #   Populate global variables
+    #
     calc_sandbox_info();
             foreach my $edep ( sort keys %{$fe->{'edeps'}} )
+            {
                 my ($ppn,$ppv) = split( $; , $edep);
                 Message ("        E:$ppn $ppv");
+            }
+        }
+    }
+    #
     #   External dependencies flags
+        }
+    }
 #DebugDumpData ("depends", \%depends );
 #DebugDumpData ("External Depends", \%extern_deps );
+    #
     #   Determine package build order
     #       Scan the list of packages in the build set and determine
     #       those with no dependencies. These can be built.
                 "help:+"        => \$opt_help,
                 "manual:3"      => \$opt_help,
                 ) || Error ("Invalid command line" );
     SubCommandHelp( $opt_help, "Command $cmd") if ($opt_help );
+    #
     #   Insert default options
+    #
     push @build_opts, '-noforce' if ( $cmd eq 'all' );
     push @build_opts, '-force' if ( $cmd ne 'all' );
             my ($pn,$pv) = split( $; , $pve );
             Message ("Cache ${pn} ${pv}");
             JatsTool ('cache_dpkg', "${pn}/${pv}" );
+        }
+    }
     exit 0;
+}
 #-------------------------------------------------------------------------------
 # Function        : populate
+#
 # Description     : Determine the PVID for a given package name and version
+#
 # Inputs          : $pname          - Package name
 #                   $pver           - Package Version
+#
 # Returns         :
+#
 sub getPkgDetailsByName
+{
     my ($pname, $pver) = @_;
 jats_sandbox - Build in a Development Sandbox
 =head1 SYNOPSIS
-  jats sandbox [options] {command} [command options]
+  jats sandbox [options] command [command options]
  Options:
     -help[=n]          - Display help with specified detail
     -help -help        - Detailed help message
     -man               - Full documentation
     cache               - Cache external dependent packages
  Use the command
     jats sandbox 'command' -h
  for command specific help
 =head1 OPTIONS
 =over 8
 =item B<-help[=n]>
 Print a brief help message and exits.
 There are three levels of help
 =over 8
+=item   1
-=item   1 Brief synopsis
+Brief synopsis
+=item   2
-=item   2 Synopsis and option summary
+Synopsis and option summary
+=item   3
-=item   3 Detailed help in man format
+Detailed help in man format
 =back 8
 =item B<-help -help>
 The create command simply places a known directory in the current directory.
 This directory is used by the sandboxing process. It may be manually deleted, or
 deleted with the 'delete' command.
 =head1 Populate Sandbox
 =head2 NAME
 Populate a Sandbox
 Options not understood by the 'populate' sub command will be passed through
 the package extraction program. Useful options include:
 =over 8
+=item *
-=item   -extractfiles
+-extractfiles
+=item *
-=item   -branch=<branch name>
+-branch=<branch name>
 =back
 =back
 The 'populate' command can be used to assist in populating the sandbox. It has
 two modes of operation.
 =over 8
+=item 1
-=item Named Package
+Named Package
 If the user specifies both a package name and a package version then he command
 will populate the sandbox with that package and optionally its dependencies.
+=item 2
-=item Determine missing dependencies
+Determine missing dependencies
 If the user does not specify a package name and version, but does specify
 the '-missing' option,  then the command will examine the current sandbox and
 determine missing dependent packages. It will then populate the sandbox with
 these packages and optionally there dependencies.
 =head2 EXAMPLES
 =over 4
+=item *
-=item jats sandbox populate package1 version1
+jats sandbox populate package1 version1
 This command will populate the sandbox with version1 of package1, if it does not
 already exist in the sandbox.
+=item *
-=item jats sandbox populate package1 version1 -recurse -missing
+jats sandbox populate package1 version1 -recurse -missing
 This command will populate the sandbox with version1 of package1, if it does not
 already exist in the sandbox, together will all the packages dependencies that
 are not available in a package archive.
+=item *
-=item jats sandbox populate -recurse -missing
+jats sandbox populate -recurse -missing
 This command will examine the current sandbox and populate the sandbox with
 packages that are required to build the packages in the sandbox and the
 dependencies of these packages, provide the dependent package is not in a
 package archive.
+=item *
-=item jats sandbox populate
+jats sandbox populate
 This command will examine the current sandbox and populate the sandbox with
 packages that are required to build the packages in the sandbox. It will not
 examine the dependents of these packages.
     -verbose[=n]            - Verbose command operation
  Command Options
     -help[=n]               - Command specific help, [n=1,2,3]
     -verbose[=n]            - Display more information
 =head2 OPTIONS
 =over
 =item B<-verbose[=n]>
 The command works within various levels of verbosity:
 =over 8
+=item *
-=item * No Verbosity
+No Verbosity
 The basic command will display the build order and the external
 dependencies. External dependencies may be prefixed with one of the
 following indicators:
 =over 8
-=item   +   Multiple versions of this package are being used by sandboxed components.
+=item   '+' Multiple versions of this package are being used by sandboxed components.
-=item   *   The package cannot be found in any of the package archives.
+=item   '*' The package cannot be found in any of the package archives.
 =back
+=item *
-=item Verbosity of 1
+Verbosity of 1
 This level of verbosity will display the build order and detailed information
 on the dependencies. The dependencies will be prefixed with:
 =over 8
-=item   E   Dependent Package is external to the sandbox
+=item   E Dependent Package is external to the sandbox
-=item   I   Dependent Package is internal to the sandbox
+=item   I Dependent Package is internal to the sandbox
 =back
 External dependencies may be prefixed with one of the indicators described for
 no-verbosity. Additionally the internal consumer of the external package is also
 shown. These are prefixed with a 'U'.
+=item *
-=item Verbosity of 2
+Verbosity of 2
 Reserved for future use
+=item *
-=item Verbosity over 2
+Verbosity over 2
 This should be considered a debug option. Undocumented internal information will
 be displayed.
 =back
 This command may be used to:
 =over 8
+=item *
-=item * Pickup any build file changes.
+Pickup any build file changes.
+=item *
-=item * Resume a failed build.
+Resume a failed build.
 =back
 =head1 Command build

Subversion Repositories DevTools

(root)/core_devl/trunk/TOOLS/jats_sandbox.pl – Rev 359 → 361