Hm. If I had the desire to be creating rpms yes. But why should I go through that extra hassle? There is a very clear answer for this: It is the clean way. Servers that are supposed to run stable, should be set up in a clean way. The more often you leave the path of the package system, you are on the way to
Suse is generally a good choice for the desktop. As well for servers. Even if SuSE received a lot of criticism for 8.0 with removed yast1, etc., they are still a good server distribution too. The /etc/sysconfig approach makes it even just better than any suse before (I don't have to use YaST anymore for setting up the network, because the syntax has become sane, finally). I guess if I could automate going from source to keep the hassle level down, and make it a Suse rpm that would be ideal. yes. grab the xxx.src.rpm from the DVD, copy your new version of xxx to
On Wed, 8 May 2002, Steve wrote: trouble. It's in the same category as "Backup" and "Documentation": Some people may live without these things for years without a single problem. But in fact it is dangerous, and lot of hard work is wasted, if something goes wrong. the sources directory, change and rebuild the spec file and you are there. Security has its price, and a clean and consistent system is one of the things you should pay for. Markus -- _____________________________ /"\ Markus Gaugusch ICQ 11374583 \ / ASCII Ribbon Campaign markus@gaugusch.at X Against HTML Mail / \