Hi John, As long as the hammer does the job. At this stage although I'm aware that RPM packaging is much more powerful my lack of knowledge about it doesn't allow for a more sensible approach.
Hopefully this will change time ;) thanks, Duarte 2009/11/12 John Dennis <jden...@redhat.com>: > On 11/12/2009 12:28 PM, Duarte Fonseca wrote: >> >> Hi John, >> >> The only change I did to the spec file was change the release (and >> later add the --enable-developer) >> >> What I did do was go to the SOURCES dir and unpack the >> freeradius-server archive, change the file in question, pack up >> freeradius-server replacing the original tar.bz2 archive. >> >> I did this assuming rpm build would build using whatever code is in >> that tar.bz2 file. Is this another case of assumption being the mother >> of all f*ckups? > > You can do it this way, but it's like trying to use a hammer to drive a > screw :-) The whole rationale of RPM packaging is based around applying > patches to upstream sources, which in this instance is exactly what you're > doing. > -- > John Dennis <jden...@redhat.com> > > Looking to carve out IT costs? > www.redhat.com/carveoutcosts/ > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
