Chapter 6. Uploading and Maintaining Custom Packages
33
6.2.2. Using the RHN Push application
Note
It is recommended that you create at least one private channel to receive custom pack-
ages prior to upload, since a channel is required for systems to obtain the packages.
The following command uploads package headers to the RHN Satellite Server and copies
the packages to the RHN Satellite Server package repository:
rhnpush -c
label_of_private_channel pkg-list
You can override the settings in your
RHN Push
configuration file(s) by specifying options
and values on the command line:
rhnpush -c
label_of_private_channel
--server localhost
pkg-list
The
label_of_private_channel
is the custom channel created to receive these
packages. Be sure you use the precise channel label specified during its creation. If you
have one or more channels specified (using
-c
or
--channel
), the uploaded package
headers are linked to all the channels identified. If you do not specify a channel, the pack-
ages are deposited in the
No Channels
section of the
Package Management
page. Re-
fer to Section 4.6
Assigning Packages to Software Channels
for instructions on reassigning
packages.
The
--server
option specifies the server to which the packages are installed, and is re-
quired.
RHN Push
can be installed on external systems, but running
RHN Push
locally
on the RHN Satellite Server is recommended.
The
pkg-list
reference represents the list of packages to be uploaded. Alternatively,
use the
-d
option to specify the local directory that contains the packages to be added
to the channel.
RHN Push
can also read the list of packages from standard input (using
--stdin
).
