
Option Description
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
--source. Using --source --newest together does
update the stand-alone source package with newer
packages and does not require an associated binary
package to be uploaded first.
--source 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.
--stdin Read the package names from standard input.
--nosig Don't fail if packages are unsigned.
--no-ssl Turn off SSL (not recommended).
--stdin Read the package names from standard input.
--username USERNAME Specify RHN username. If not provided, you are
prompted for the username of a valid Channel
Administrator.
--password PASSWORD Specify RHN password. If not provided, you are
prompted for the password of a valid Channel
Administrator.
--dontcopy In the post-upload step, do not copy the packages to
their final location in the package tree.
--copyonly Only copy the packages, do not re-import them.
--test Only print a list of the packages to be pushed.
-?, --help Display the help screen with a list of options.
--usage Briefly describe the available options.
--copyonly Only copy packages
Table 6.1. rhn_package_manager options
Tip
These command line options are also described in the rhn_package_manager
Chapter 6. Uploading and Maintaining Custom Packages
28
Komentáře k této Příručce