Archaic wrote these words on 05/16/06 19:00 CST:
> However, the gaim page also shows libtasn1,
> which technically isn't needed because libtasn1 (and opencdk, for that
> matter) are included in the gnutls tarball.
Not sure if your mention of my name is good or bad, but I'll take
it as good. :-)
JK. Yes, I've tried to outline sometimes a dependency chain when one
exists for a Non-BLFS package. However, seems I've also listed libtasn1
and opencdk somewhere else. As you mention, they are not required
because they are included in the GnuTLS tarball, but it's my belief
that including them is a good thing.
Otherwise folks may end up installing the packages via the GnuTLS
tarball, and if they had known, they would have done it the {B}LFS
way.
Though to be really technically correct, the text would read something
like:
GnuTLS (which requires x, y, and z, and can also use a and b)
--
Randy
rmlscsi: [bogomips 1003.27] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686]
19:01:01 up 4 days, 11:01, 2 users, load average: 0.00, 0.00, 0.00
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
