swcopy - Copy distribution
No additional rationale is required under this heading.
This utility may be used to perform the following tasks:
- Copy software from one distribution to another
- Merge software from one distribution into another
- Copy software to a temporary distribution located to improve swinstall reliability or performance
No additional rationale is required under this heading.
No additional rationale is required under this heading.
No additional rationale is required under this heading.
No additional rationale is required under this heading.
The swcopy utility operates much like the swinstall utility. The key distinction between swcopy and swinstall is the way products are loaded. With swcopy, products are not installed for general use below the root directory. Instead, they are placed into a distribution, which can then act as a source for swinstall.
Update Capabilities
Unlike installation where products can not exist in the same location at the same time, every product that differs in any one of the revision, architecture or vendor_tag attributes is treated as a separate version of the product and does not update or overwrite any other version. Thus, when a newer revision of a product is copied into a depot, it does not in any way affect the older revision. As covered previously, swinstall will automatically choose the highest revision unless the revision explicitly specified.When the same revision of a fileset within the same product version is being copied, it is considered a "recopy". The fileset is skipped unless the "recopy" option is set to true, just as is done with the reinstall option to swinstall.
- Example:
- swcopy -x recopy=true PRODUCT.FILESET,r=<same>
This will recopy all files in the fileset.
If the same product version has been repackaged so that attributes of the same product version (that is, same revision, architecture and vendor_tag), are different between the new product instance being copied in and the existing product instance, then the values of the new product are retained. The values of any attributes in the old product that are undefined in the new product are also retained.
An update within a depot is not clearly defined in 1387.2 (updates of filesets within existing product version are usually only needed during the development phase of a software product). Released products will generally have new revisions, or patches to a current revision.
Copy the software_selections listed in /tmp/load.products other default values defined in the /var/adm/sw/defaults file) as follows:
- swcopy -f /tmp/load.products
Remove a product Foo from the distribution on the tape device /dev/rct0 as follows:
- swcopy -s /dev/rct0 \* @ /tmp/depot" swremove -d Foo @ /tmp/depot" swcopy -s /tmp/depot \* @ /dev/rct0"
Example of reinstall_files:
- swcopy -x reinstall_files=false
Another example of reinstall_files:
- swcopy -x reinstall_files=false reinstall_files_use_cksum=falsed
Examples of patch specification:
- Example:
- swcopy -x autoselect_patches=true X11,r=6
Copy X11,r=6 software from one depot to another and also copy all patches for that base software.
- Example:
- swcopy -x autoselect_patches=true \ -x patch_filter="*,c=critical"
Copy all software from a depot and also copy a filtered set of patches (those with a category of "critical"), for the base software.
- Example:
- swcopy -x patch_match_target=true
Copy from a depot containing patches and also non-patch software, all patches for the base filesets which are already present in the target depot.
- Example:
- swcopy -x patch_match_target=true -x patch_filter="*,c=critical"
Copy from a depot containing patches and possibly also non-patch software, a filtered set of patches for the base filesets which are already present in the target depot.
No additional rationale is required under this heading.
No additional rationale is required under this heading.
| Contents | Next section | Index |