From: Didier C. <did...@gm...> - 2005-08-31 15:44:43
|
On 8/31/05, Michael Jennings <e-...@ka...> 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 go= od thing > > imho. can you turn it OFF? a BUILD may require edje-devel but runtime i= t may > > not need it. >=20 > 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. >=20 > > hmm rpm has gone downhill - this above is bad imho. there are cases > > where it will be wrong. >=20 > 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). >=20 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. --=20 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. |