On Monday May 21 2007 09:36:10 pm Randy McMurchy wrote:
> 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

Libcap is similar to Cracklib, in that nothing actually depends on it, and it 
provide an enhancement. The problems with Libcap is that 1) it's not 
maintained, and 2) the packages that can use it mark it as experimental. 
Libcap may not be the best candidate for inclusion in the BLFS book, and it 
doesn't bother me to make an LFS hint for it. I suggest it for the BLFS book 
because there are more than one packages that can use it, and it's the ideal 
place for it. Alternatively, something like this would make good use of the 
BLFS wiki.

robert

Attachment: pgpLDONb7y2QJ.pgp
Description: PGP signature

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to