FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Portage Developer

 
 
LinkBack Thread Tools
 
Old 05-15-2012, 11:15 AM
Pacho Ramos
 
Default About some settings to auto-replace with dispatch-conf

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
 
Old 05-15-2012, 03:31 PM
Zac Medico
 
Default About some settings to auto-replace with dispatch-conf

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
 
Old 05-15-2012, 07:43 PM
Pacho Ramos
 
Default About some settings to auto-replace with dispatch-conf

El mar, 15-05-2012 a las 08:31 -0700, Zac Medico escribió:
> 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.

Didn't know about that option, thanks for pointing it

About trying to enable it by default, I think would make sense per
previous exposed reasons (and I am sure there are more examples that
could show that behavior is better than keeping obsolete config files by
default)
 
Old 05-15-2012, 07:46 PM
Pacho Ramos
 
Default About some settings to auto-replace with dispatch-conf

El mar, 15-05-2012 a las 21:43 +0200, Pacho Ramos escribió:
> El mar, 15-05-2012 a las 08:31 -0700, Zac Medico escribió:
> > 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.
>
> Didn't know about that option, thanks for pointing it
>
> About trying to enable it by default, I think would make sense per
> previous exposed reasons (and I am sure there are more examples that
> could show that behavior is better than keeping obsolete config files by
> default)
>

Just noticed the problem of current behavior after updating my chroot to
generate emul packages and needing to review 40 files with
dispatch-conf, all of them never touched and all of them needing to be
updated to new version
 

Thread Tools




All times are GMT. The time now is 05:40 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org