Den 16:16 20. desember 2011 skrev Jeffrey Johnson <n3...@me.com> følgende: > > On Dec 20, 2011, at 9:55 AM, Per Øyvind Karlsen wrote: > >> Den 17:39 21. oktober 2011 skrev Jeff Johnson <j...@rpm5.org> følgende: >>> RPM Package Manager, CVS Repository >>> http://rpm5.org/cvs/ >>> ____________________________________________________________________________ >>> >>> Server: rpm5.org Name: Jeff Johnson >>> Root: /v/rpm/cvs Email: j...@rpm5.org >>> Module: rpm Date: 21-Oct-2011 17:39:03 >>> Branch: rpm-5_4 Handle: 2011102115390101 >>> >>> Modified files: (Branch: rpm-5_4) >>> rpm CHANGES >>> rpm/macros macros.rpmbuild.in >>> rpm/scripts find-debuginfo.sh >>> >>> Log: >>> - debuginfo: use current dir instead of $RPM_BUILD_DIR. >> D'oh, a bit late discovered, but better than never.. >> >> $RPM_BUILD_DIR == %{_builddir} >> while >> $PWD == %{_builddir}/%{?buildsubdir} >> >> So for most packages which have their own %buildsubdir, this will mess >> up the paths for debug packages, ie. see the following example: >> > > I hope "… have their own %buildsubdir …" doesn't mean that some > package monkey is trying to set/change %builddubdor in a *.spec file. Nope, I'm referring to whether %buildsubdir is set or not (as controlled by %setup). For most packages it's set, with the default being %{name}-%{version}. So "%{_builddir} / %{buildsubdir}" will be ie. "/usr/src/rpm/BUILD / foo-1.2.3". > > Meanwhile, I'm not sure what you have "discovered": literally nothing has > changed in this area for most of this century, the whole mechanism > if fabulously broken and mis-designed and mis-implemented imho. Simply that $PWD == %{_builddir}/%{?buildsubdir}, thus $RPM_BUILD_DIR=`pwd` is incorrect with the consequence of messing up paths in debug packages..
-- Regards, Per Øyvind ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List rpm-devel@rpm5.org
