On Mon, Aug 21, 2017 at 09:58:18PM -0500, Bruce Dubbs wrote:
> Ken Moffat wrote:
> > On Mon, Aug 21, 2017 at 04:32:25PM -0500, Bruce Dubbs wrote:
> > > I was going though all the perl modules for blfs-8.1 and have have some
> > > issues with two modules.
> > > 
> > > 1. Scalar::List::Utils is not found by cpan.  The current comments say 
> > > that
> > > this module is not needed with perl-5.26 which is, of course, in lfs-8.1.
> > > 
[...]
> > 
> > For what I've added in the perl modules, when a package becomes
> > needed, or not needed, I try to keep it in the book for some time so
> > that anybody building current versions of packages using perl modules
> > (particularly biber) on an older BLFS can still continue.
> > 
[...]
> 
> But if a users are using an old version, shouldn't they go to an older
> version of BLFS?
> 
No, only the versions in -dev get security updates.  Even for
*binary* texlive we've had a vulnerability fix in the past year.

[...]
> 
> > > 2.  SGMLSpm has been in the book for a long time, but I do not know where 
> > > it
> > > is used.  cpan does not recognize it although it can be downloaded.
> > > I did find a note on blfs-dev from 2010 that gnome-power-manager uses it,
> > > but I could find no reference in the current version.
> > > 
> > > Is there any reason to keep this around?
> 
> > Dunno - I've always built all of the docbook-related packages soon
> > after booting.  I'll try without it in my next builds - those won't
> > be for a few days.
> 
> I don't think the perl module SGMLSpm has anything to do with
> docbook-related packages.  Am I missing something?
> 
It just happens to be where I build it in _my_ scripts, SGML is
docbook, after all.

ĸen
-- 
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
                                     - Unseen Academicals
-- 
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