filesystem hierarchy

Joerg Sonnenberger joerg at britannica.bec.de
Tue Nov 14 13:03:10 PST 2006


On Tue, Nov 14, 2006 at 09:56:59PM +0100, Eli Green wrote:
> On 2006-11-14, Joerg Sonnenberger wrote:
> >On Tue, Nov 14, 2006 at 08:57:02PM +0100, Eli Green wrote:
> >>It seems to me that DragonFly is not very far from the stated goal of
> >>having multiple libraries as it is, using varsyms or maybe a slightly
> >>specialized version of nullfs:
> >
> >[snip]
> >
> >(a) As Jeremy said, this is something pkgviews tries/tried to do.
> >(b) This is a *huge* maintainance hassle.
> >
> >It works for Debian using the 1000 monkeys approach, but it doesn't work
> >for a reasonable large (as in: small) team. E.g. keep in mind that it
> >means splitting a single package into small pieces for the static
> >libraries, header files, associated programs etc., as everything but the
> >shared lib will conflict in the filesystem. This is a wonderful
> >nightmare.
> >
> 
> I don't understand why it would require packages to be broken up like
> that. If anything, you wouldn't want that... the include directories
> would be part of the same structure.

Otherwise you start either symlink hell or can't support it with many
packages as they simply expect a different structure.

Joerg





More information about the Users mailing list