On Friday 06 December 2002 18:57, Fran�ois Pons wrote:
> Le ven 06/12/2002 � 18:11, Jesper Krogh a �crit :
> > Hi. I have a suggestion.
> >
> > The current layout of urpmi.cfg file is this way:
> > secure {
> > hdlist: hdlist.secure.cz
> > with_hdlist: ../base/hdlist.cz
> > list: list.secure
> > update
> > }
> >
> > entities.
> >
> > It would be wery nice if all relevant information was stored in the
> > urpmi.cfg file, so you could copy it to another system and do a:
> > urpmi.update -a
> > and it would retrieve the hdlists if they were accessible.
>
> It is the case (url) now, except if a user/password is visible inside
> it.
Ok, I have updated, now i looks more like I'd expect it to do.
> > Due to the current layout of configuration files for urpmi, is it quite
> > impossible to view the configuration and verify that it is as I would
> > expect it to be. And even more impossible to copy a complete
> > configuration to another system ( if I don't have the exact
> > urpmi.addmedia commands ).
>
> Not enough simple ?
Exactly. Now I have this entity in /etc/urpmi/urpmi.cfg:
secure ftp://ftp.sunet.se/pub/os/Linux/distributions/mandrake/updates/9.0/RPMS
{
hdlist: hdlist.secure.cz
with_hdlist: ../base/hdlist.cz
update
}
If i remove:
/var/lib/urpmi/hdlist.secure.cz
And run:
urpmi.update secure I get:
unable to access hdlist file of "secure", medium ignored
But thats not true... it could just get it from the Ftp it knows.
And a second suggestion. The possibility to have more than one server defining
the same sources. So I wont miss if my local mirror reboots when my cronjob
runs urpmi.update.
But urpmi is really shaping up and looks very good.
Thanks.
--
Jesper Krogh, [EMAIL PROTECTED]
