On 19.04.2006, at 14:25, Denis Solovyov wrote: > > ... > I find easier to just download source from software's site, examine > ./configure --help, and then just ./configure --options && make && > make install. Once you select the necessary configure options, and > you'll almost never need to think of anything again (just casting a > glance at ChangeLog from time to time).
I go through that hell on my tsl development machine quite often, but as soon as I have figured out how it works, I create rpms, since if there is an update, I just add the patch and rebuild, no need to patch the source on every machine that I maintain. The resulting can be used on any other TSL machine, if I did everything correct, the configure --enable-foo --disable-bar --enable-xxxlib=/usr/local/lib can't be done on every machine. how do you port your compile from server to server? (and make sure www1 and www2 have the same libaries/apache patches installed?) I think rebuilding from source is calling for lots and lots of hours of software that can be used by installing from rpm. I even have a suse desktop machine, and if I like how the programme is compiled there, I take a look in the spec file, and test the options on my devel server, so easy, just a line .... just my two cents ... m ps: I work for a tv station part time, compiling ffmpeg, gpac, x264, mplayer from source (including libraries) would be not doable if I wouldn't have rpm to remind me of the settings and patches ... pps: OT: if somebody did it to compile vlc from source, please tell me how ... _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
