Paul Rogers wrote:
For perl modules, I generally used the cpan method. It still uses
source, but the builds, including dependencies, are automated.
My usual technique is to build up my system until I reach the need for
the first perl module. Then I install them all in alphabetical order.
The only one I've needed so far has been the XML-Parser, and I did that
one individually. AFAIK, there's no need on the immediate horizon, just
seems like a good point to take care of it--"in for a penny, in for a
pound." I did get and tarball the bunch at
http://anduin.linuxfromscratch.org/sources/BLFS/svn/perl-modules/.
What would be the best way to capture the order CPAN does things in,
thinking along the lines of getting it from a tee'd console log perhaps?
That would work or you could just create a build tree manually from the
dependencies in the book.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
