[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: fedora-extras-release

Nils Philippsen wrote:

On Sat, 2005-02-05 at 18:33 -0500, Jim Cornette wrote:

Justin Georgeson wrote:

Matthias Saou writes:

Too bad though that it seems sysconfig/rhn/ can only take info from the
single "sources" file, as from my understanding this means that the current
RHN notification tool won't automatically be aware of Extras after this
package is installed.

Add a post install script that does

echo "..." >> /etc/sysconfig/rhn/sources

and a post uninstall script that does

grep -v "..." /etc/sysconfig/rhn/sources > /tmp/sources.new
mv /etc/sysconfig/rhn/sources.rpmsave
mv /tmp/sources.new /etc/sysconfig/rhn/sources

You could add some 'if [ $? != 0 ]; ...' stuff to rollout the changes if a
command fails, but it would mean that up2date can use Extras and the rhn_applet
will se updates.


fedora-extras-list mailing list
fedora-extras-list redhat com

I'd me more in favor of the script checking the /etc/sysconfig/rhn/sources to see if an entry exists, then appending the entry into the file if there are no entries for fedora-extras. I use up2date a lot and use specific mirrors that I would not like to have bothered.

Oh it would be so much better if you could just put some keyword like "yumconf" into sources and up2date would read the repositories from /etc/yum.conf or /etc/yum.repos.d/*.conf.


Diverting up2date over to use a common file for configuring mirrors seems to be a better approach than to worry about the need to configure the listings in both config files. I would prefer this scheme over touching up2date configuration files, appending data, etc to anotger program's config file.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]