On 11/04/2018 06:36 PM, Ken Moffat via blfs-dev wrote:
I think that the perl modules branch (perl dependencies broken down
into those modules directly referenced by other packages in the book,
and a second page of those which are only there as dependencies of
other modules) are now ready for testing by the brave, and for
review.
Rendered versions at:
http://www.linuxfromscratch.org/~ken/perl-changes/
The date is 2nd November because I have only merged trunk changes up
to r20669.
If you use cpan to install modules, this does not apply to you and
you will continue to get whatever dependencies upstream lists,
whether or not they are useful (e.g. sometimes use of a package is
removed but in lingers in the prerequisites, other times a
dependency extends the test coverage but the tests will still pass
without it).
Ken, I appreciate all the work you put into this. As you know, I
generally use the cpan method to install modules. During the BLFS
release process I generally build all the perl modules when I get to the
first requirement.
One question I have is what are the consequences of using the cpan
install for LWP::Protocol::https? That does not use the patch. As best
I can tell, a grep for LWP::Protocol::https only shows up in biber and
then only in XML comments. Can you clarify?
-- Bruce
At this point, there are probably some errors. In particular, I
note that HTTP::Form has dropped out of the libwww-perl
dependencies. That *appears* to be correct, but it looks
suspicious and I won't be able to test that myself until I build a
fresh system. That is perhaps a week away, I need to update my own
scripts (to match the book) first, and then test building biber.
For all modules, dependencies should be built in the listed
(alphabetical) order - some deps are pulled in by multiple modules,
and for any given module my aim is to only list them once.
Similarly, if you run the tests (for a few years I have tested most
perl modules, but I can see that omitting tests will save time) the
dependencies are written on the assumption that you will pick a
top-level module and run tests both for it and all its dependencies,
so things like e.g. Test::Warnings might only be mentioned in one of
the dependencies, even though the top-level module also needs it for
its tests.
There may still be issues with biber (perhaps, missing test
dependencies if the perl modules are built without those, or issues
with remote https:// links to bibliographies in the absence of
Mozilla::CA - that should work, but all my systems where biber can
be built already have that installed, so again I'll need to do a
fresh system build to test that.
But if you build perl modules without using cpan, please take a look
at this. Thanks.
ĸen
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
