Red Hat NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT Manual de usuario Pagina 37

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 40
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 36
Option Description
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 first.
--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 Briefly 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.
2.2. Using the RHN Push application
Note
It is recommended that you create at least one private channel to receive custom
packages prior to upload, since a channel is required for systems to obtain the
Using the RHN Push application
31
Vista de pagina 36
1 2 ... 32 33 34 35 36 37 38 39 40

Comentarios a estos manuales

Sin comentarios