Quote:>Or upgrade to a complete 3.3.3 system via RedHat's rpms. For 5.2, ftp to
>updates.redhat.com, and go to the /5.2/i386 directory. I found I needed to
>delete some of the packages, because somebody moved some files around.
Thanks for the advice. But having to delete some files as you put it
is ugly! RPM should've dealt with that. Right? Who knows what state
the database is in... Maybe the package management way is not the way
The admins here at this site put non-core packages in their own
Sure, they have to manage dependencies themselves, but it works very
well, and no database to get corrupted, and to remove a package one
can just rm -rf the directory, etc. No problems upgrading a library
that other stuff depends on, etc.
Multiple people can, and do, work in those directories.
Yes, $PATH, $MANPATH and $LD_LIBRARY_PATH management can be an issue,
but I wrote a shell function and script to automate that for
myself. It's not hard to handle.
You could make symlinks to the normal places if need be (standards,
etc). Not too hard to manage the symlinks, since a simple stat() will
let you know where tehy go, and hence, what they are.
You could have every such package automatically get a window manager
menu and each program a menu entry. Same with the man stuff for help
Dealing with that is much easier than RPM, etc type
solutions. Dependencies can be dealt with with common sense.
You don't need a database, etc if your files from different packages
are all mixed up together.
Might be a good alternative to .rpm, .deb hell.
BTW, GNU software have no problem with being put in a specific
./configure --prefix=/local/packagename works well. I have done this
at multiple sites, without trouble.