04-14-2011 11:52 AM
I put the xxx.depot.gz files in /usr/temp and give this as the Source location for depot files. I have even unzipped them so they are xxx.depot files and still no joy.
How do I create a depot? It seems to be some sort of magical directory where all sw-commands look for files. I have read and studied a good paper called "Software Depot Package Builder", but it too assumes one already has a depot to begin with. I do not. This is a bare bones recently built HPUX 11.00 system with no new software attached because I cannot find a depot anywhere. I would think that if I FTP'ed a xxx.depot.gz file to the system, I would have a depot file, but they are not recognized as such. Can anyone help answer what I expect is a dumb question once I see an answer?
Solved! Go to Solution.
04-14-2011 10:04 PM
Before using it with swinstall or swcopy, you must uncompress it first:
The result will be a .depot file in uncompressed form, which should be usable with swinstall or swcopy directly.
Note that the sw* tools will want a _full_ pathname of the depot, since they pass the actual work to the swagentd daemon, which does not have the same current working directory as your login session.
So, to list the contents of the depot:
swlist -s /full/path/of/your.depot
(you can add options like "-l product", "-l fileset" or "-l file" to get more detailed listings)
To install software from a depot:
swinstall -s /full/path/of/your.depot
To install *everything* from a depot:
swinstall -s /full/path/of/your.depot \*
You should also know that a depot can have two forms: a file/tape depot, or a directory depot.
Before CD-ROMs, HP-UX software was distributed on magnetic tapes. The .depot file format is essentially a tape image file. A file depot can be used for local installations and swcopy operations only: it cannot be accessed remotely from another HP-UX system.
A file depot can be converted into a directory depot with swcopy:
swcopy -s /full/path/of/your.depot \* @ /full/path/of/directory_depot
If a directory depot does not exist, swcopy will automatically create it.
You can add the contents of multiple depot files to a single directory depot, and then install everything with only one swinstall operation (and with only one reboot, if one is necessary). A directory depot can also be accessed remotely, if its swacl permissions allow remote access (and by default, they usually do).
To install software from a remote directory depot, just add "remote_hostname:" to the source specification:
swinstall -s remote_hostname:/full/path/of/directory_depot
By the way, you don't need a graphics card on your system to use SAM or any X Window System applications: if you have another system that can run X server software (e.g. a Windows workstation with ReflectionX or free Xming), you can use it as your display.
SAM and the swinstall tools also have a text-based menu interface: if your DISPLAY environment variable is not set and your TERM variable correctly specifies the type of your terminal or terminal emulation, the swinstall tools and SAM should automatically switch to using an ASCII-art based user interface.
04-16-2011 02:25 AM
Why would you use SAM when you can use swinstall CLI?
>I have even unzipped them so they are xxx.depot files
What does "file xxx.depot" show? It should show "tar" for depots.
>How do I create a depot?
You don't. They should already be depots.
>paper called "Software Depot Package Builder", but it too assumes one already has a depot to begin with. I do not.
SPB and swpackage create depots. swcopy copies them.
>if I FTP'ed a xxx.depot.gz file to the system, I would have a depot file
Yes, or a gzipped one.
>MK: want a _full_ pathname of the depot, since they pass the actual work to the swagentd daemon
I've always assumed that if it wasn't absolute, it was the name of a machine. Not because of swagentd(1m).
>the swinstall tools also have a text-based menu interface
Better to just use the CLI.
04-19-2011 06:31 AM
I had no depots on my system. In other words, swlist -d depot returned none. I tried swcopy to no avail. It kept saying there were no depot fils at my source. (I thought swcopy was for copying existing depots files only).
Anyway I used swpackage to cteate a depot and it succeeded. I thank all of you for responding.
04-19-2011 05:46 PM
swcopy -x enforce_dependencies=false -s /tmp/PHXX_1234 \* @ /var/tmp/mydepot
The directory (/var/tmp/mydepot) is created automatically and the depot file is then added. You then repeat for additional depots. This is how you merge many patches together to form a single installation depot. Don't forget the \* (or "*") that specifies use everything in the depot.
04-23-2011 08:57 AM
>Anyway I used swpackage to create a depot and it succeeded.
Created from what? You should only use swpackage to create tape depots or depots from raw files.
04-25-2011 09:37 AM