Hi Roger,
Am 07.04.2009 um 08:08 schrieb Roger Håkansson:
And those broken RPATH/RUNPATHs was due to a bug in gar, not what
the maintainer might have set (or not set).
To be precise here: The method $ISALIST was passed was due to
multiple expansion, where the number of expansions depended on
the package and it was the responsibility of the maintainer to
ensure proper quoting. It was my fault to not have made this
clear and give advice on how to properly set it.
Since we have established that its not harmful to have RPATH set
even when its not used, I can see more problem (as in more work for
the maintainer in the future) with actively unsetting LD_OPTIONS
than not.
It is possible to include other ways of passing -R to the linker
that don't interfere with what the maintainer intended. We can
work on these cases when they occur.
If package A is linked to a lib i package B (both CSW packages)
and A i
packaged with RPATH/RUNPATH set to only /opt/csw/lib, any future
releases of B which contain optimized libraries won't be used
until A is
repackaged with RPATH/RUNPATH set to /opt/csw/lib/$ISALIST:/opt/
csw/lib
Correct. Add $ISALIST in, unless you know it won't be needed.
And my point is that you can't know if its going to be needed or not
at the time of package (unless you are both maintaner of A and B and
know that you won't package optimized version of B).
That's why GAR adds $ISALIST per default, both in the old version
and now. If you don't want it you have to turn it off, the unaware gets
optimizations.
Best regards
-- Dago
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
