Michal Jaegermann wrote:
On Tue, Mar 11, 2008 at 02:30:23PM +0900, John Summerfield wrote:
Michal Jaegermann wrote:
Here we come again to a "config" problem. /etc/inittab is marked as
a configuration file. Even if that would get translated that would
not help you at all as on the next update all these translations
would be silently clobbered. Those files likely should be even
"config noreplace".
I don't see a problem with translating /etc/inittab when upstart is
first installed.
You are clearly missing the point. There are no essential problems
with translating on the first installation. There are troubles
What did I just say? Did you see "first installed?"
with keeping those translations intact across upstart updates.
Or you are proposing to keep /etc/inittab indefinitely as a kind
of a "master" configuration and run those translations every
time upstart is updated? That does not sound very appealing.
Having done the translation, hide
inittab with the usual rename.
And what happens the next time when an update showed up? Keep in
mind that your translations are not marked as configuration files.
It's not the first time upstart is installed, and inittab is hidden by
being renamed. Since it's hidden, it remains as documentation against
the possibility the translation was inadequate.
It doesn't seem to me you're understanding what I'm trying to say.
Michal
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
