
/opt/ignite/bin/make_bundles
Note:
With this form of the command you cannot give the bundles you are creating a name. The most useful form of this command involves giving the
In this example, you create some of the same bundles that were created in previous examples. However, this time you use an explicit list of products to include (or patches in this case):
#make_bundles
> /var/opt/ignite/depots/Rel_B.11.23/patches
#ll ./PB_Sept_2007_1.0.psf
1 root | sys | 951 Aug 31 16:46 ./PB_Sept_2007_1.0.psf |
#make_bundles
> /var/opt/ignite/depots/Rel_B.11.23/patches
#ll ./PB_Sept_2007_1.1.psf
1 root | sys | 1015 Aug 31 16:47 ./PB_Sept_2007_1.1.psf |
You can now apply the commands stored in these two PSF files against the depot. When you do, you end up with the same results as with the make_bundles first form:
#swlist
#Initializing...
#Contacting target "test"...
#
#Target: test:/var/opt/ignite/depots/Rel_B.11.23/patches
#
# Bundle(s):
#
patches | 1.1 | /var/opt/ignite/depots/Rel_B.11.23/patches |
patches | 1.0 | /var/opt/ignite/depots/Rel_B.11.23/patches |
With the third form, you cannot specify an explicit name. You must edit the PSF to change the name of the bundle.
Tip:
If you use change control it is better to generate a PSF and place it under change control than to use make_bundles to generate a temporary PSF and apply the changes to the depot. By placing the PSF in your change process, you know exactly how a bundle wrapper in a depot was created and what was in it. This allows you to, at some later time, recreate bundles exactly as they were before.
34