On Wed, 27 May 2009 00:35:59 +0200 Bill Allombert <[email protected]> wrote:
> Furthermore, this issue will be fixed with a new sourceful upload, which is > the > only sane way to fix the build system. This is delayed in the hope of a new > upstream version in July. How realistic is that hope? > > > There is no need to > > > NMU libjpeg to include this broken patch. > > > The patch is not wrong - it works just fine and it is completely > > insulated from the Debian builds. > > You mean the patch you sent *today* ? How was I supposed to apply it before? The patch is essentially the same as the one previously sent - I just tweaked it a bit for readability. The effect of the patch is completely unchanged. > Anyway I refuse to apply any patch which cause the upstream libtool > to be used in any way. On what basis? The change is never enacted within Debian. > > rpath is not an issue for Emdebian - I don't care what happens with it, > > it simply doesn't matter within the context of Emdebian installations. > > But I do, because this is a policy requirement. A Policy requirement that applies to Debian but Debian does not accept packages that are cross-built and the rpath only shows up *IF* the package is cross-built so there is no problem here. It is Emdebian Policy that rpath *is* set in some circumstances, as explained in my other email. This patch does *not* change the Debian build, it does not introduce rpath into the Debian packages and it does not break Debian Policy. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
pgpP3yGFp069j.pgp
Description: PGP signature
