Installed location of a package

[Vibhor Kumar Agarwal]

Hi,

I have created test package named Test.
How do i figure out the installed location of package.

Was doing "swlist -l file Test" and it stated
/opt/Test/Test.txt
If I relocate the package to /abc, then also swlist -l file is giving /opt as the location.

Now how do i figure the installed location?
Thanks

[sreekanthtm]

Hi,

My thoughts....
Swlist pick the information from its owm database created while installing the package. So, if you are relocating the file manually, that won't afect the swlist o/p. You need to slecify the installation location while installing the pkg.

Rgds,
Sreekanth.

[Vibhor Kumar Agarwal]

The package is already installed at the relocated location of "/abc/Test".

Now if a new user comes, how does he determine the location of the package.

[Dennis Handly]

>how do I figure the installed location?

From within a control script?
http://docs.hp.com/en/5992-5875/ch11s04.html#v2215294
SW_LOCATION
SW_ROOT_DIRECTORY

[Vibhor Kumar Agarwal]

Yes,

I am aware of that. I want to find the location of the package after it has been installed.

Say a 2nd person.

[Dennis Handly]

>I want to find the location of the package after it has been installed.

I would hope swlist would tell you that. Otherwise it would be next to useless.
You may have to use -v to see which attribute.

[Vibhor Kumar Agarwal]

Probably the "location" attribute in "swlist -v" gives the installed location.

But shouldn't "swlist -l file " point to the location where the binaries are installed?

[Sajjad Sahir]

Dear Friend

swlist -v
List all the attributes for an object if no -a options are specified. (Vendor-defined attributes are not included. See the -a option.) The output lists one attribute per line in the format:

attribute_name attribute_value

thanks and regards

Sajjad Sahir

[Bill Hassell]

> If I relocate the package to /abc, then also swlist -l file is giving /opt as the location.

relocate?

Di you simply move the /opt/pkg to /abc? If so, kyou have disconnected all information about the package from swlist. swlist will show where it WAS installed. After that, any changes to directories cannot be tracked. You would have to remove the package and reinstall it with swinstall but specify the new location. Then swlist will show where it was installed.

[Vibhor Kumar Agarwal]

I installed it via normal relocation install:

swinstall -s Test,l=/abc/Test

Even then "swlist -l file Test" shows
/opt/Test/Test.txt

[Dennis Handly]

>Even then "swlist -l file Test" shows
/opt/Test/Test.txt

Hmm, this seems broken.
And the -v doesn't have /abc/Test anywhere?

[Vibhor Kumar Agarwal]

It has

The "location" attribute of "swlist -v" shows /abc/Test.

Shouldn't "swlist -l file Test" also show files are under /abc?

[Dennis Handly]

>The "location" attribute of "swlist -v" shows /abc/Test. Shouldn't "swlist -l file Test" also show files are under /abc?

I can only assume that by changing only location, all of the IPD entries can be left alone.

[Vibhor Kumar Agarwal]

Sounds weird.
There are gurus of packaging here. Anybody having more ideas.

[Dennis Handly]

I tried a small example and it is as you said.

If you want the installed location you are going to have to glue lines:
$ swlist -l file -a location SwPackager_dummy
# SwPackager_dummy /var/tmp/FIREFOX_stuff/YUK
# SwPackager_dummy.SPB-HELP_dummy /var/tmp/FIREFOX_stuff/YUK
/var/tmp/stuff/sin.c

Where sin.c is in:
/var/tmp/FIREFOX_stuff/YUK/var/tmp/stuff/sin.c

[Vibhor Kumar Agarwal]

You meant to say it's happening the way this whole post is about?

I couldn't get your example.

[Dennis Handly]

>it's happening the way this whole post is about?

Yes and it looks like it's by design.

>I couldn't get your example.

The PSF had: /var/tmp/stuff/sin.c

swinstall ... SwPackager_dummy,l=/var/tmp/FIREFOX_stuff/YUK

[Vibhor Kumar Agarwal]

Probably a bad design.

Thanks for all your efforts.