Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Aug 2014 00:06:30 +0200
From:      Mathieu Arnold <mat@FreeBSD.org>
To:        Kurt Jaeger <pi@FreeBSD.org>
Cc:        perl@freebsd.org
Subject:   Re: perl 5.20 and .bs files, Mk/Uses/perl5.mk
Message-ID:  <9F2411058DF788C4740876DA@atuin.in.mat.cc>
In-Reply-To: <EC43415872E6D6A2F6FD605B@atuin.in.mat.cc>
References:  <20140817195800.GQ42528@f10.opsec.eu> <EC43415872E6D6A2F6FD605B@atuin.in.mat.cc>

next in thread | previous in thread | raw e-mail | index | archive | help


+--On 17 ao=C3=BBt 2014 23:20:31 +0200 Mathieu Arnold <mat@FreeBSD.org> =
wrote:
| +--On 17 ao=C3=BBt 2014 21:58:00 +0200 Kurt Jaeger <pi@FreeBSD.org> =
wrote:
|| Hi!
||=20
|| Can you give me a hint on this ?
||=20
|| The logic of
|=20
| The .bs files are bootstrap files, thatis, files needed on a few obscure
| cases to know what shared objects to load when having to delay loading =
the
| shared object of a perl module. (it's as close as I can make it in a
| sentence, also as close as I understand what it does.)
| Those files have always been empty (and thus useless) on FreeBSD. =
Starting
| with Perl 5.20, the bootstrap files are not installed any more if they =
are
| empty.
|=20
| So, this removes them for older Perl too, to be consistent. (When I added
| Perl 5.20, I did full builds, checked all the packages for .bs files, =
they
| were *all* empty.)
|=20
|| fails for devel/p5-File-Map -- even with a 5.20 perl, there is a
|| .bs file left over in STAGEDIR. Is this a bug in the perl module
|| and do I have to remove it in post-stage: ?
|=20
| What do you mean fails ? Is the .bs file empty ? If it is, then, yes,
| there is a bug, if it is not, then, there is no bug, and it should be
| packaged.

Having a look at it, nothing fails, everything works as expected[1], only
the File::Map author must be doing something strange, and manages to get
Perl 5.20 to install a bootstrap file. (Which is not anything fatal, it's
just a stray file lying there[2].)

I'd say remove it in post-install, but this needs a bit more inspection to
see exactly why this port behaves differently than the thousands other we
have that work just fine.

1:
https://pkg.absolight.fr/data/10amd64-pkgng-perl5-20/20140804T043250Z/logs/p=
5-File-Map-0.61.log
2:
https://pkg.absolight.fr/data/10amd64-pkgng-perl5-20/20140817T235221Z/logs/p=
5-File-Map-0.61.log
--=20
Mathieu Arnold



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9F2411058DF788C4740876DA>