On Fri, Nov 29, 2013 at 07:28:53AM -0800, John Reiser wrote:
/usr/bin/unpack200: RPATH=$ORIGIN
(a) Are these bugs? They seem to be.
RPATH=$ORIGIN is not a bug. It is a correct and thoughtful usage,
I deliberately left this one in because it does look like it needs
inspection. AIUI it
On Fedora 20 (beta-ish), I did:
for f in /usr/bin/*; do chrpath -l $f ; done | grep RPATH /tmp/rpaths.txt
I removed from the final list private library RPATHs, which are
permitted[1]. Here is the final list:
/usr/bin/afm2tfm: RPATH=/builddir/build/BUILD/texlive-2013/source/inst/lib
On 11/29/13 at 12:15pm, Richard W.M. Jones wrote:
On Fedora 20 (beta-ish), I did:
for f in /usr/bin/*; do chrpath -l $f ; done | grep RPATH /tmp/rpaths.txt
I removed from the final list private library RPATHs, which are
permitted[1]. Here is the final list:
/usr/bin/afm2tfm:
/usr/bin/unpack200: RPATH=$ORIGIN
(a) Are these bugs? They seem to be.
RPATH=$ORIGIN is not a bug. It is a correct and thoughtful usage,
one that even allows for moving the whole package after install.
--
--
devel mailing list
devel@lists.fedoraproject.org
On 11/29/2013 04:28 PM, John Reiser wrote:
/usr/bin/unpack200: RPATH=$ORIGIN
(a) Are these bugs? They seem to be.
RPATH=$ORIGIN is not a bug. It is a correct and thoughtful usage,
one that even allows for moving the whole package after install.
It still looks like an accident because
On Fri, 29 Nov 2013, Richard W.M. Jones wrote:
|
| On Fedora 20 (beta-ish), I did:
|
| for f in /usr/bin/*; do chrpath -l $f ; done | grep RPATH /tmp/rpaths.txt
|
| I removed from the final list private library RPATHs, which are
| permitted[1]. Here is the final list:
|
| /usr/bin/afm2tfm:
On 29/11/13 14:59, Pavel Zhukov wrote:
On Fri, 29 Nov 2013, Richard W.M. Jones wrote:
| (b) I thought Fedora had an RPM install post script which was supposed
| to detect these and alert the packager?
Right now it doesn't have such script.
Well it does, in rpm-build is