Red Hat NETWORK 4.0.5 - Przewodnik Instalacji Pobierz pdf (Strona 36)

32 Chapter 6. Uploading and Maintaining Custom Packages

Option Description

--newest 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 --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 ﬁrst.

--header Upload only the headers.

--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.

--server SERVER Specify the server to which packages are uploaded.

Currently, a value of http://localhost/APP is

necessary. This parameter is required.

--test Only print a list of the packages to be pushed, don’t

actually push them.

-h, --help Brieﬂy describe the options.

-?, --usage View the usage summary.

Table 6-2. rhnpush options

Tip

These command line options are also described in the rhnpush manual page: man

rhnpush.

1 2 ... 31 32 33 34 35 36 37 38 39 40

Brak uwag

Red Hat NETWORK 4.0.5 - Przewodnik Instalacji Strona 36