Red Hat NETWORK 4.0 - CHANNEL MANAGEMENTT GUIDE Manual page 32

28
Option
-l, --list
-s, --sync
-p, --printconf
--newest
--source
--stdin
--nosig
--no-ssl
--stdin
--username USERNAME
--password PASSWORD
--dontcopy
--copyonly
Chapter 6. Uploading and Maintaining Custom Packages
Description
List the packages in the specified channel(s).
Check if local directory is in sync with the server.
Print the current configuration and exit.
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
Package Manager 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
--newest
source package with newer packages and does not
require an associated binary package to be uploaded
first.
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.
Read the package names from standard input.
Don't fail if packages are unsigned.
Turn off SSL (not recommended).
Read the package names from standard input.
Specify RHN username. If not provided, you are
prompted for the username of a valid Channel
Administrator.
Specify RHN password. If not provided, you are
prompted for the password of a valid Channel
Administrator.
In the post-upload step, do not copy the packages to
their final location in the package tree.
Only copy the packages, do not re-import them.
. Using
--source
together does update the stand-alone
--source