On 8/31/05, Michael Jennings <[EMAIL PROTECTED]> wrote: > On Wednesday, 31 August 2005, at 16:25:14 (+0900), > Carsten Haitzler wrote: > > > > weird. its a build requires. it should not think this. this is not a good > > thing > > imho. can you turn it OFF? a BUILD may require edje-devel but runtime it may > > not need it. > > No, it's not a good thing. Fortunately, it's not true either. :-)
Damn I should have specified "If needed" ! This makes more sense to the explanation. Thanks to Ignacio and Michael for enlightening this matter. > > > hmm rpm has gone downhill - this above is bad imho. there are cases > > where it will be wrong. > > Then it's a good thing it doesn't actually happen, eh? :) RPM will > only pull in run-time dependencies based on build-time dependencies if > it detects a run-time dependency as a result (like library linkage). > Precisely. :-) That's why we DON'T need obvious Requires. If let' s say you' ve placed edje-devel as BuildRequires and the program needs edje to run, it will know that. You don' t need to overstate that. If it doesn' t need edje to run, it will simply not *pull* out the package. -- 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
