Robert Connolly wrote: > > I understand BLFS, and LFS, tries to be vanilla and avoids using non-official > patches or configurations, but libcap is no longer maintained and there will > be no more upstream fixes.
This in itself is enough to keep it from the book, IMHO. We don't need unmaintained packages in BLFS. I've always installed libcap, but only to satisfy strange requirements by packages. Until recently, it wasn't even mentioned in the BLFS book as an optional component. The governing fact, however, will be what it provides to a BLFS package. I don't need to know *what* package uses it, I want to know how it helps a BLFS package become better. What does this package add? How does it help BLFS packages that reference it as a dependency? Please, understand I'm looking for specific references that enhance a package. Just because a couple (few) BLFS packages reference libcap as an optional dependency does not mean that it automatically qualifies the package for inclusion in the book. There must be something substantial that libcap provides, to include it as a package we promote. Please, Robert, expand on how libcap helps the various packages that use it as a dependency. -- Randy -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
