On Wed, 27 May 2009 00:39:36 +0200 Bill Allombert <[email protected]> wrote:
> On Mon, May 25, 2009 at 08:27:12PM +0100, Neil Williams wrote: > > Emdebian Crush doesn't use the libjpeg-progs_6b-14em1_arm.deb package, > > only the shared library matters. > > > > n...@holly:libjpeg6b-6b$ readelf -d > > ./debian/libjpeg-progs/usr/bin/cjpeg|grep RPATH > > 0x0000000f (RPATH) Library rpath: [/usr/lib] > > > > You haven't precisely described the actual issues you are using to > > discount this bug report and I've done what I can to show that the > > patch allows the package to cross-build without any ill effects, either > > in Debian or Emdebian. AFAICT there is no basis for using arguments > > based on RPATH because it plainly is not a problem. > > Not a problem for you, but it might be a problem for someone else that > crossbuild the package. An rpath of /usr/lib is a clear policy violation. Only of Debian Policy but Debian Policy does not make any claims about cross-built packages because cross-building isn't the way that Debian builds packages. (Cross-built packages are not welcome in the archive.) Emdebian has our own Policy which departs from Debian Policy in certain areas - one of which is rpath. The simple reason is that the problems that rpath causes in Debian are not applicable within an embedded system. rpath is a fact of life in the embedded world, there is no use-case for removing it and no problems caused by retaining it in a system built from cross-built packages. Indeed, in many ways, Emdebian *requires* rpath to be set in some circumstances. See: http://wiki.debian.org/EmdebianPolicy Besides, as shown in the output, the rpath is only set in the programs in the -tools package which, again, is of no relevance to Emdebian or other embedded deployments. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
pgpdWoCYcGJmo.pgp
Description: PGP signature
