On Sat, 2004-09-11 at 20:23, Ville Skyttà wrote: > On Sat, 2004-09-11 at 20:39, Arjan van de Ven wrote: > > On Sat, 2004-09-11 at 19:09, Ville Skyttà wrote: > > > Is there another reason besides rpm automagic stripping (+ laziness or > > > something like that in not resetting to 644 in the specfile later) for > > > all *.ko to be executable by root (mode 744) in the kernel package? > > [Apologies, this sounded more foul than it was supposed to...] > > > well..... the stripping happens during the final rpmbuild stage; I don't > > have scripts running after that, it's pure RPM itself from that point on > > You can always "reset" the attributes using %attr in %files. One > solution would be to create a file list during the "find" in > BuildKernel(), and use that later on, something like this (definitely > incomplete and buggy, but just to throw in the idea): ok now it's my turn .. ;-) is having the modules executable an actual problem? If so in what scenario ? Before going down a semi complex and probably somewhat fragile road I'd like to be sure there's a real problem getting fixed by something like this and not just something cosmetical...
Attachment:
signature.asc
Description: This is a digitally signed message part
