On 8/31/05, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote: > On Wed, 31 Aug 2005 12:02:26 +0800 Didier Casse <[EMAIL PROTECTED]> > babbled: > > > On 8/29/05, Jim Perrin <[EMAIL PROTECTED]> wrote: > > > Quick patch to a couple Makefile.am's in embrace to allow it to make > > > dist cleanly, and a spec file to aid in rpm packaging. > > > -- > > Hi Jim, > > Thanks. However I've a tiny remark: when you have have a > > package X-devel in BuildRequires, then it obviously Requires X. There > > is no need to specify the Requires. It's stating the obvious. RPMS > > are smarter than you think. :) > > not necessarily - if all you need is some TOOL from the -devel. eg - you need > edje_cc to compile .edj's as part of the build process - but you don't need it > runtime :) :)
Maybe I expressed myself wrongly or wass too quick at writing something. RPM has very good capabilities of automatically finding dependencies for libraries. e.g if you state that package X: BuildRequires: edje-devel Only stating this would imply for a tool like yum/apt to automatically download edje for RUNNING the application. i.e if you type: yum install X Then you will get X depends on edje... ready to download. 1.edje 2. X Proceed? now if you want to rebuild X src rpm, then it will tell you that you need edje-devel to rebuild it. So it comes back to me saying that putting something like this; BuildRequires: edje-devel Requires: edje is NOT necessary. RPM will download the non-devel package automatically. But something like this is OK: BuildRequires: edje-devel Requires: xine Now this means that it doesn't require xine-devel to BUILD but requires xine to RUN. In such a system, a yum install X would download: 1. edje 2. xine 3. X http://fedoraproject.org/wiki/PackagingGuidelines#Requires -- With kind regards, Didier. ------------ Yum/apt repository for DR17/EFL: http://sps.nus.edu.sg/~didierbe Didier F.B Casse PhD candidate, Singapore Synchrotron Light Source (SSLS) National University of Singapore. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
