Hi Drew, > 1) Is the idea to apply the dependency symlinks to packages beyond LFS?
I guess BLFS would be the main target for this, as base LFS doesn't supply dependency information. If dependency information was found for packages in LFS, the system could be used there too. I've started implementing in BLFS, and so far it seems to do what I want. > 2) What do you do about nested dependencies? For instance, when > building QGIS, there is at least one package, PostGIS, requires three > others -- but two of those (IIRC) are also needed by QGIS itself. That is fine, as the symlinks only propagate to nearest-neighbours, so you won't get two symlinks to QGIS appearing in the packages that PostGIS depends on. PostGIS will have a link to QGIS in its reverse-depends, and links to the packages it depends on in its depends. Two of those packages it depends on will link to both PostGIS and QGIS in their reverse-depends. QGIS will simply list PostGIS and those other two packages in its depends. > 3) What about libraries that several packages depend upon? The reverse-depends directories can have as many symlinks in them as you want :-) Cheers, Tim -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
