MandrakeUpdate is an update tool - It doesn't install new packages. Both the
"Installed" version and the "Update" version are displayed. Try `rpm -qa |
grep <package-name-minus-version>` if you don't belive this.

> especially since many rpms for
> services will start the service without notifying you.

In LM 7.2 you can control this using msec. There is an option to disallow
RPMS from adding themselves to your startup scripts

> I feel better knowing *most* of whats installed on the machine, there is
> no need for me to update BitchX or install it if I had a reason not to put
> it there in the first place.

If you're not going to update it, I recommend removing it (rpm -e BitchX).
If MandrakeUpdate sees it, it is already installed.

> Adding an
> option to the updater that performed a freshen operation would be most
> useful.

Once again - what does it say in the "Installed" version column? The updater
already works like this.

> A command line version (which has been discussed already)
> would also be a wonderful addition, not only for the headless among us,
> but also to be able to use the updater in remote management scripting
> solutions (hint, hint if anyone at MandrakeSoft happens to read this far)

One possibility is to use ncftp to keep a fresh local mirror of the updated
RPMS. Default usage of ncftp won't re-download files that are already
present. You can then use the good ol' `rpm -Fvh *.rpm` I personally don't
run cron jobs to do the actual update - rpm doesn't handle dependencies will
enough for me to trust it. An NFS mount of the local mirror can be used to
keep all of the systems on your network updated.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]