This package, from what I can make of it, is a great addition to linuxconf!
Since I can't find a helpfile though (see my email with subject "help files
missing"), it's very difficult to try and use this tool. If someone could
direct me to the helpfile, that would be tremendous; otherwise I have a
couple of questions about the functionality.
The biggest pain with managing rpms is keeping up to date with the updates
(i.e., errata) from the vendors (e.g., RH). A brilliant way of handling this
would be to compare a list of packages that are currently installed with
those that are available at an update site (e.g.,
ftp://ftp.alpha1.net/pub/redhat/updates/5.1/i386/). If there's a package
that is a later version, then it would basically "store" that update
somewhere (e.g., "rpm -Uhv
ftp://ftp.alpha1.net/pub/redhat/updates/5.1/i386/packagename-1.1.1.i386.rpm"
). After compiling a list of packages that need updating, it would then
iterate over them to double check dependencies such that either additional
packages would be installed or the package updates would be re-ordered to
best match the dependencies. After all this is done, it could send an email
to the administrator telling him/her that there are rpm updates waiting to
be done. Then, the admin could bring up linuxconf and tell it to implement
the updates, which would then execute this "script" that would have been
created above.
Does the current implementation do anything like this? As I am writing this,
I am installing the source to the module to study it in detail. I still
would very much like to get a hold of the helpfile though.
Thanks!
Sean Stoner
HYPERCON, INC.
"Internet Solutions that make Sense"
http://www.hypercon.com
2024 Bissonnet St.
Houston, TX 77005
713-528-2400
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jacques Gelinas
> Sent: Tuesday, October 20, 1998 8:25 AM
> To: Linuxconf Mailing List
> Subject: [linuxconf] Re: managerpm
>
>
> On Fri, 16 Oct 1998, aurelio marinho jargas - ctba wrote:
>
> >
> > > > maybe it should test the RPM dir you especify as soon as you
> > > > put the entry to it on the Preferences menu, and not when
> > > > you try to install/update a package from the other itens.
> > what about that?
>
> Well, when you set the preference, one path may not be available. For
> example, on a redhat system, one may set /mnt/cdrom/RedHat/RPMS and the CD
> may not be mounted at this time. So validation is not always possible.
>
> >
> > > Not sure I follow you. When you enter a directory, it does not expect
> > > sub-directories at all. It uses the wildcard spec (*.rpm by
> default) to
> > > scan the directory directly. It does not even rely on
> *.386.rpm. I mean,
> > > you can take one file say
> > forget about it, i was doing the mistake, passing a dir and
> > not a path/pack-name.rpm to the Install/Update one package
> > menu.
> >
> > and on the Install/Update many packages i can't pass the dir
> > of the full distribution cause segfault.
> >
> > but passing a dir with less rpms, all ok.
>
> Ok, it will be fixed in the next release of managerpm. There were a bug
> both in the module and in linuxconf. So an upgrade to both will be needed.
> Check the announce...
>
> --------------------------
> Jacques Gelinas
> [EMAIL PROTECTED]
>
>
>
>
>
> ---
> You are currently subscribed to linuxconf as: [EMAIL PROTECTED]
> To unsubscribe, forward this message to [EMAIL PROTECTED]
>
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
