tldr; for "second class" perl modules used by multiple other perl
modules, I've moved t hem to the top level in the perl modules page,
but without any version number.

I'm (still) in the process of building the individual biber
dependencies using cpan to install each on a minimal system (and
then backing them out).  For biblatex-biber-2.6 there are a lot more
of them.

I've already found a few errors (modules which are already present
in core perl with suitable versions, one missing dependency), but I
noticed a lot of low-level modules used by many things.  Where a
module is "external" (i.e. we don't have a versioned entry in the
book) the XML is deeply nested for dependencies.  This simple editing
monkey finds it hard to notice that there are links to some random
module if it is not at the top level of the page (i.e. name in bold
type, in alphabetical order).

What I've now done is move those modules which have multiple
references only on this page (Capture::Tiny, XML::LibXML, XML::SAX)
to the top level, but without a version, md5sum, built/checked tag
or versioned download.

This doesn't of itself reduce the deep nesting, but it provides some
minor help.

I cannot see any reason to make them first-class versioned citizens
in the book, that will just add to the churn.

Unfortunately, the XML is still deeply nested, and I'm not looking
forward to adding the new biblatex-biber-2.6 dependencies when I've
sorted them out.  Using cpan seems to have installed a *lot* more
dependencies for DateTime::TimeZone than I needed in my manual build,
but even without those I had 24 new modules).

Now that I have a spare system with only the core perl modules, using
cpan to check dependencies (and also to find things which are no
longer needed) is possible, but tedious, and I do not intend to do it
frequently.

ĸen
-- 
`I shall take my mountains', said Lu-Tze. `The climate will be good
for them.'     -- Small Gods
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to