How to create one file file_name.depot with swpackage

[Alex Landman_3]

First question:
I always see, that HP Patches come packaged in one file, ussualy
file_name.depot.
I can create depot with swpackage, but what I get is directory build with all
files inside.

How can I get just one file?

Second question:
I have created a depot, and I can easily install my product on the local
machine. Right after I can see my product on swlist screen.
Wnen I mounted my registered depot to another machine, and installed same
product there, I don't have any errors, but I don't see it on swlist screen.
What possibly may goes wrong?

[Evan Day_1]

Those .depot files are really just tarfiles of the directory you get from
swpackage. If you tar up the depot directory to a file on disk you've got the
exact same thing.

As for your second question, is the software actually installed on your remote
system? Try passing swlist the "-l fileset" switch to list every fileset on
the system. AFAIK, if the fileset doesn't show up in swlist it probably isn't
installed correctly, if at all.

[Alex Landman_3]

Thanks a lot for previous response.

I possibly do something wrong, because it still doesn't work.

I have tried to create .depot files by changing some default options for
swpackage such as compress_type, compress_cmd, but there is no option for
changing file extensions to *.depot)

I also tarred the depot directory after creating a package, but then swreg and
swinstall doesn't recognize the product or depot...

It seems to me that setting some flags, or changing default options can be done
by changing some default flags or options, but I didn't find this kind of
information in HP documentation

[mark alexander]

First, a single-file depot is actually a tape format depot. If you already have a product in a depot, you can copy it to a file with:

swpackage -x target_type=tape -s /path/to/depot mypkg @ /path/to/file.depot

Second, you shouldn't have to "mount" your depot on your other machine. swinstall ins network aware. You can just do:

swinstall -s depot_host_name:/path/to/depot

That bring up the swinstall selection screen with your remote host as the source. If your depot is not registered, it may not work (depending on your patch level , I think). If not, you can register it by running (on the depot host):

swreg -l depot /path/to/depot

More info in the man pages for swpackage and swreg.

[Joel Shank]

HI
I use swcopy to create a depot "seen" by all my other servers. After swpackage creates the "depot", try using swcopy to make a complete depot (all patches are contained in it). Swcopy will also automatically register the depot it creates. I do it this way and never have problems.

Good Luck
JLS