Hi,
> I've been thinking about a construction some time now, and that's using the
> extended attributes to identify a package. This is a variant of the hint
> "more_control_and_pkg_man.txt" by Matthias Benkmann.
This sounds really good. I don't think about using these for primary
way of telling what package file belongs to, but as backup of database
that can be easily rebuilt using simple find command...
> The only problem is how to set these attributes when installing a package
> and all of the files that belong to this package.
> I'm thinking of wrappers for all the commands that create files:
> install,cp,mv....
What about LD_PRELOAD? You can use checkinstall to track created files
and then simply attr them.
> IMHO the idea of an extra database containing all the information about
> packages installed is not good: the filesystem your system is on itself is
> a database and should contain this information. The only question is howto
> find it.
I don't agree with this. Using database is *much* faster. On my box it
takes more then three minutes to `find /`, not saying it puts disk under
very high load. Even package users suffers from this.
I have different proposal, lets install under package user to ensure
nothing gets destroyed with complete logging using checkinstall. When
package is installed, set extended attributes so we can tell package
from the file and then record all it's files in DB. If DB is damaged or
outdated, package list can be rebuilt using `find`.
To install packages smoothly create build scripts similar to gentoo's
(with use flags and basic dependencies). This all can be written in BASH
with maybe some bits of perl to speed up things.
If you like this, mail me and I'll help you with that as I'm not going
to write it alone althou I've already tried. I just get bored too soon. ;]
With head high in clouds,
Mordae
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
