[arch-dev-public] rc.conf cleanup why?
Hi http://projects.archlinux.org/initscripts.git/commit/?id=5b062674869c9701887... I don't think this is a good idea, I liked the described options in rc.conf. Now you have to switch to an other terminal to read what options are possible. pacman.conf and makepackage.conf also have comments on important options, so why remove parameters from the most important config file? greetings tpowa
Am 19.07.2012 07:58, schrieb Tobias Powalowski:
Hi http://projects.archlinux.org/initscripts.git/commit/?id=5b062674869c9701887... I don't think this is a good idea, I liked the described options in rc.conf. Now you have to switch to an other terminal to read what options are possible.
pacman.conf and makepackage.conf also have comments on important options, so why remove parameters from the most important config file?
Probably a matter of taste. Personally I like my config files without comments; it just gives you a better overview. Greetings, Pierre -- Pierre Schmitz, https://pierre-schmitz.com
Tobias, I'd like to nudge people into thinking twice before using these options. In addition to documenting what options exist, the man page also explains why you should not use them. As of the next release initscripts will do the right thing when rc.conf is empty. I also started adding warnings whenever people have contradictory/nonsensical options specified (usually solved by deleting the options). Tom On Jul 19, 2012 7:58 AM, "Tobias Powalowski" < tobias.powalowski@googlemail.com> wrote:
Hi
http://projects.archlinux.org/initscripts.git/commit/?id=5b062674869c9701887... I don't think this is a good idea, I liked the described options in rc.conf. Now you have to switch to an other terminal to read what options are possible.
pacman.conf and makepackage.conf also have comments on important options, so why remove parameters from the most important config file?
greetings tpowa
I should add: the reason I prefer manages rather than comments is that they can be more verbose and updated more frequently. On Jul 19, 2012 11:55 AM, "Tom Gundersen" <teg@jklm.no> wrote:
Tobias,
I'd like to nudge people into thinking twice before using these options. In addition to documenting what options exist, the man page also explains why you should not use them.
As of the next release initscripts will do the right thing when rc.conf is empty.
I also started adding warnings whenever people have contradictory/nonsensical options specified (usually solved by deleting the options).
Tom On Jul 19, 2012 7:58 AM, "Tobias Powalowski" < tobias.powalowski@googlemail.com> wrote:
Hi
http://projects.archlinux.org/initscripts.git/commit/?id=5b062674869c9701887... I don't think this is a good idea, I liked the described options in rc.conf. Now you have to switch to an other terminal to read what options are possible.
pacman.conf and makepackage.conf also have comments on important options, so why remove parameters from the most important config file?
greetings tpowa
participants (3)
-
Pierre Schmitz
-
Tobias Powalowski
-
Tom Gundersen