On 1 July 2012 05:12, Ian Stakenvicius <a...@gentoo.org> wrote:
> Do all packages need to be rebuilt when some of these use flags
> change? Maybe auto-appending those particular flags (ithreads, debug)
> to IUSE and putting them on the dev-lang/perl dep is all that'll be
> needed, if this is the case.
Not all packages need rebuilding, but *every* package with XS parts
need rebuilding, as code built with DEBUG/ITHREADS enabled will not
execute on perls with different DEBUG/ITHREADS options. ( And as a
preventative measure, they're installed in entirely different dirs )
@INC:
/etc/perl
/usr/local/lib64/perl5/5.16.0/x86_64-linux <- binary
/usr/local/lib64/perl5/5.16.0
/usr/lib64/perl5/vendor_perl/5.16.0/x86_64-linux <-- binary
/usr/lib64/perl5/vendor_perl/5.16.0
/usr/lib64/perl5/5.16.0/x86_64-linux <-- binary
/usr/lib64/perl5/5.16.0
.
.
( At least, the dir name switching used to be a thing, I can't see it
in the code anymore so I could be wrong, I don't tend to twiddle those
USE flags often )
Also, it would appear that in some cases ( ie: dev-perl/Mouse ) , they
don't install any binary code , but the .pm files themselves are
installed into the x86_64-linux folder, which, if that path is removed
from @INC when you rebuild perl with different USE flags, will break
them, despite not having any binary code.
But either way, if "SlotABI" is supposed to convey "A change that can
occur to a package that means other packages that were built on it
need to be rebuilt" , then this is something we need.
--
Kent
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"
http://kent-fredric.fox.geek.nz
