On 11 July 2011 16:21, Andreas Jaeger
On Monday, July 11, 2011 17:15:20 Rob OpenSuSE wrote:
2) Suggestion about text file contents with lines like "enable, disable" which create ordering problems.
I don't see an ordering problem! Where do you see it?
People were asking questions like, what supercedes what if in file it's both enabled & disabled etc etc. The discussion looked more and more compicated to me, with some intricate proposals with many levels, or involving file naming conventions; even character set was considered, hence the "numbering" rather reminscient (ironically) of S10*, S20* & K90*, K80* examples in current /etc/init.d script links.. Either single file to check, or simple flags in 2 directories are both workable solutions. I realise if it were formal proposal, that a better presented worked out alternative would have been better. It was simply that I saw "beauty" in minimalist simplicity of making flags flags and the useability of such is very obvious to me. What would be horrible is many files, with flags in them like "enable", "disable". The inherent disadvantage with flags in packages is they then own their defaults, where they differ from distro "global" policy for some good reason. It may not matter, but there's not some central point with overview of which package does what, unless it's collated. They can however respect the site global policy by checking for prescence of local "global" over-ride flag, which could for example in openSUSE, SLE & Fedora be set by default to enforce the "all off" on install policy quite neatly. I just hope the final solution, has simpler rules easy to understand that are simple to remember, to avoid confusion or mandate use of GUI for overview. Rob -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org