From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] About some settings to auto-replace with dispatch-conf
Date: Tue, 15 May 2012 08:31:38 -0700 [thread overview]
Message-ID: <4FB276DA.3000901@gentoo.org> (raw)
In-Reply-To: <1337080552.3731.8.camel@belkin4>
On 05/15/2012 04:15 AM, Pacho Ramos wrote:
> Hello
>
> I recently installed Gentoo on my uncle's laptop and he was a bit
> annoyed about needing to run "dispatch-conf" and merge a lot of changes
> on files nobody ever touched.
>
> Looking to /etc/dispatch-conf.conf I noticed options to improve this
> situation exist, but they are disabled by default. I would want to
> confirm if they are safe enough or could cause problems. Options are:
>
> # Automerge files comprising only whitespace and/or comments
> # (yes or no)
> replace-wscomments=no
>
> # Automerge files that the user hasn't modified
> # (yes or no)
> replace-unmodified=no
>
> Looks really surprising to me that "replace-wscomments" is not enabled
> by default as merging that changes shouldn't hurt at all. About
> "replace-unmodified", if it works as intended, it should also be safer
> to get it enabled by default as would prevent breakage if people forgets
> to run dispatch-conf, reboot and, for example, sees some init.d script
> fail to start.
>
> Thanks a lot for the info
FEATURES=config-protect-if-modified is what you really want. We could
probably enable it by default, but we should ask for comment on the
gentoo-dev mailing list before doing that.
--
Thanks,
Zac
next prev parent reply other threads:[~2012-05-15 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 11:15 [gentoo-portage-dev] About some settings to auto-replace with dispatch-conf Pacho Ramos
2012-05-15 15:31 ` Zac Medico [this message]
2012-05-15 19:43 ` Pacho Ramos
2012-05-15 19:46 ` Pacho Ramos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FB276DA.3000901@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox