Install of all packages

John HEARNS <[email protected]>
Newsgroups gmane.network.up2date.current.devel
Message-ID <1026898116.6950.24.camel@ues4>
Dear All,
me again. Sorry - you must be sick of my questions!

Here is a snippet of my current.conf

[CERNCC]
label = CERN-CC
name = CERN Computer Centre addons
parent_channel = 
arch = i386
os_release = 7.2
description = RPMs which FIO group make to add to interactive and batch
machines

rpm_dirs = /afs/cern.ch/project/linux/redhat/pro/addon/cc/RPMS/i386
           /afs/cern.ch/project/linux/redhat/pro/addon/cc/RPMS/noarch

xrpm_dirs = 
src_dirs = 
db_dir = /var/current/redhat-7.2/CERN-CC/current



My aim is that when we create new, extra packages for our machines that
these will be automatically installed when up2date is run on the
clients.
I think I got some fundamentals of the up2date mechanism mixed up.

Say I create a package called CERN-CC-package
I then put it in the appropriate (...addon) directory then re-create the
channel.  So far, so good.
However, up2date -u does not automatically install a package which is
not already on the system.
I've tried wildcards like   up2date --nox -u *  which doesn't work.

Any ideas maybe for a work-around?

I'm no Python hacker - but I will try to look in the sources of up2date.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.