On Tue, Nov 27, 2018 at 10:54:44AM -0600, Bruce Dubbs via blfs-dev wrote: > On 11/27/2018 10:07 AM, Pierre Labastie via blfs-dev wrote: > > > 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. > > There are pros and cons to a dedicated version. First, the dedicated > version is known to work with git. Second, the installation is completely > automated. Dedicated versions are only really appropriate if no other > application is using the module. > > The only con I can think of right now is that an upstream perl fix of a bug > that affects git's use of the module will not be in place until upstream git > installs it. Not all upstream releases are bug fixes. Some are enhancements > that may not be needed by git. > > -- Bruce > Either we continue as now, except that we archive Error.pm, or, I think, we will need to separately install Git.pm as well as Error and Mail::Address.
If we do the latter, presumably we somehow have to set NO_PERL_CPAN_FALLBACKS. Doing that should ensure that anyone whose git usage requires these modules will get an error if they have not installed them: BUG: The '%s' module is not here, but NO_PERL_CPAN_FALLBACKS was set! Git needs this Perl module from the CPAN, and will by default ship with a copy of it. This Git was built with NO_PERL_CPAN_FALLBACKS, meaning that whoever built it promised to provide this module. You're seeing this error because they broke that promise, and we can't load our fallback version, since we were asked not to install it. If you're seeing this error and didn't package Git yourself the package you're using is broken, or your system is broken. This error won't appear if Git is built without NO_PERL_CPAN_FALLBACKS (instead we'll use our fallback version of the module). If BLFS does that (and I have not tested how that NO_PERL... should be set), the three modules would then become recommended, because there is a simple way to use the shipped versions. ĸen -- If a man stands before a mirror and sees in it his reflection, what he sees is not a true reproduction, but a picture of himself when he was a younger man. -- de Selby -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
