patch bundle install

[Nyck_1]

I have had to download PHNE_37670 to fix an issue with one of my Itanium servers and as usual with these patches there are hordes of dependancies. Anyroad all has been downloaded to an area on the server and I have run the create_depot_hpux.11.23 script to create a software depot. So I can now go ahead and install this depot and it will be called BUNDLE.

So what happens in the future when I need to do this again. Once I have run the create_depot_hpux.11.23 script I will end up with another software depot called BUNDLE?

If I install this what will happen to the original BUNDLE?

[Steven E. Protter]

Shalom,

Your original BUNDLE will remain where it was.

The default configuration of SD/UX the software distributor uses the -x reinstall=false directive.

This will prevent your bundle from being overwritten.

I try not to name my bundles, BUNDLE and make it meaningful so that I can track the progress of what I have done to what system.

We have at work SEC_June_2008_Bundle to distinguish things and let a system engineer see easily which of our home made bundles is installed.

SEP

[Matti_Kurkela]

"BUNDLE" is just a default name. You can change it when you're running the create_depot_hpux.* script, if you wish.

Or you can do like I do: before running the script, I'll edit the three lines near the beginning of the script that define the default location of the patch depot to be created, the bundle name and the bundle description.

If you install several patch bundles using the default name and the later bundle does not completely supersede all the patches in the earlier one, the names of the individual un-superseded patches of the old bundle will be listed in the "software that is not a part of any bundle" listing near the end of the swlist output. Not harmful, but looks ugly to me.

As far as I've understood name "BUNDLE" will always refer to the _latest_ installed patch bundle with that name.


I tend to name the patch bundles according to their purpose: e.g. if it turns out some patches included in a Quality Pack have major warnings and HP issues a replacement, I create a bundle named "pQPKyyyymm". The name identifies the patch bundle as "post-QualityPack" of a particular QPK version. The patch description will be something like "QPK critical warning fixes, as of yyyy-mm-dd". The date in the description will indicate when the patches were downloaded.

MK

[Nyck_1]

The lines you edit would they be the following two:-

BUNDLE=BUNDLE
TITLE="Patch Bundle"

also what is the switch you specify when running the script to change the name?

[Dennis Handly · Accepted solution]

>what is the switch you specify when running the script to change the name?

If you use -h, it will tell you:
[-d ]
[-b ]
[-t ]

[Deepak Kr]

Hi,

open the script using vi

vi create_depot_hpux.11.23

change following

BUNDLE= new name
TITLE="Patch Bundle"

or

cd /tmp/patch/PHNE_37670
chmod 755 create_depot_hpux.11.23
./create_depot_hpux.11.23 -d depotname -t bundletitle


Regds,
Deepak