[Frugalware-devel] enabling services by default in upstart?
VMiklos
vmiklos at frugalware.org
Wed Jun 20 18:29:24 CEST 2007
Na Wed, Jun 20, 2007 at 04:58:15PM +0100, Alex Smith <alex at alex-smith.me.uk> pisal(a):
> I prefer enable. Usually if a user installs a package, they probably want
> it to work.
we counted the packages and finally we got that currently half of the
services is enabled by default. not less and nor more
two notes:
1) i think we missed that this question is only interesting for the devs
who may or may not overwrite this default in their packages. i mean:
changing this default or not changing it will not enable or disable any
already enabled or disabled service, just if we decide to change the
default, then we need to remove existing scriptlets if the service is
enabled and we need to add ones if the service is disabled. so we can
ask users, but do they really care? what they get is exactly the same
even after an upgrade
most of us (including me) often flame about if we should enabled alread
disabled services or not. this thread is not about it. this thread is
abou the default that may or may not be overwritten by the packagers
2) i suspect that this change would be good if we don't update the
config after changes. here is an example (by alex and by me):
say we rename udev to udevd (this is an enabled service for a user):
a) default: enable. life is easy, we rename the job and fine
b) default: disable. we need echo and sed hacks in post_upgrade. how
ugly!
the second example (this is a disabled service for a user):
say we rename bttrack to bittorrent-tracker
a) default: enable. we need echo and sed hacks in post_upgrade, so that
it'll be still disabled. how ugly!
b) default: disable. life is easy, we rename the job and fine
see? :) please correct me, but i think that Alex thinks that this change
will be good because he thought of only about udev-like services where
this change would make the life easy. profided that the amount of these
services is 50% it won't make our life harder or easier
so the question (and i know that this seems to be flameish, but i
really ask honestly): why will this be good? :)
as a personal aspect: i just say no because i don't see what will be the
benefid, while people (including me) hates changes. i mean if we change,
then we always change because we belive there will be some benefit. and
i don't see any benefits here. and of course i don't see why would this
be worse. just not better, which is enough for me to say 'no' for a
change :)
VMiklos
--
developer of Frugalware Linux - http://frugalware.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : /pipermail/attachments/20070620/eeea4123/attachment.bin
More information about the Frugalware-devel
mailing list