Using The Rhn Push Application - Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Manual

32
Option
--newest
--header
--source
--server SERVER
--test
-h, --help
-?, --usage
Table 6-2.
rhnpush
Tip
These command line options are also described in the
.
rhnpush
Chapter 6. Uploading and Maintaining Custom Packages
Description
Push only the packages that are newer than those on
the server. Note that source packages are special in
that their versions are never compared to each other.
Their newness is dependent on their associated
binary packages. Using this option with RHN Push
and just a source package does upload the package,
but the source package does not appear in the RHN
Web interface until the associated binary package
has been uploaded. Contrast this with
Using
the stand-alone source package with newer
packages and does not require an associated binary
package to be uploaded first.
Upload only the headers.
Upload the indicated source packages. Doing this
treats them as plain, stand-alone packages and not
as special source packages associated with another,
pre-existing binary package. For example, you can
use this when you want to distribute application
source to developers and testers outside of regular
source control management.
Specify the server to which packages are uploaded.
Currently, a value of
necessary. This parameter is required.
Only print a list of the packages to be pushed, don't
actually push them.
Briefly describe the options.
View the usage summary.
options
--source --newest
http://localhost/APP
rhnpush
.
--source
together does update
is
manual page:
man