On 26/11/2018 19:28, Alain Toussaint via blfs-dev wrote:
Le lundi 26 novembre 2018 à 12:24 -0600, Bruce Dubbs via blfs-dev a
écrit :
Reference:
http://wiki.linuxfromscratch.org/blfs/ticket/11246 (git and shipped
perl
modules)
http://wiki.linuxfromscratch.org/blfs/ticket/11295 (Error-0.17027
(Perl
module))
I've been looking at these tickets, but want to raise them here for
more
visibility. In #11246, Ken prefers to remove Error from the perl
modules because it is only used by git and git provides a copy in
/usr/share/perl5/Git.
I agree. Actually, I think we can just archive
general/prog/perl-modules/perl-error.xml, mark #11295 as
overcomebyevents, and mark #11246 fixed.
I do not see a need to put a comment in the git section. That sets
a
precedent to document every package that has some sort of shell
script
or an executable in /usr/libexec or in a dedicated location.
Opinions?
-- Bruce
Entirely agreed to archiving perl-error.xml
Well,
Up to now, I believed that we were trying to avoid bundled libraries in
book packages. This is a small example: Perl Error is a small standalone
library, that is bundled with git. Why should we use the bundled one? If
the Error module is in /usr/lib/perl, git will use that one. Usually,
The CPAN version of the module is slightly ahead of git bundled one
(presently, CPAN version is 0.17027, while git-2.19.1 provides 0.17025).
Actually, git also uses the MailTools perl module (for Mail::Address).
Maybe we should provide this one too. At least, the version in git is up
to date.
Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
