svn commit: r334617 - in head: . etc

[Konstantin Belousov]

On Wed, Jun 06, 2018 at 01:39:00AM +0700, Eugene Grosbein wrote:
> 06.06.2018 1:26, Konstantin Belousov wrote:
> 
> >>> I find it often very useful to do
> >>> 	(cd src/etc/rc.d && make install)
> >>> Same for defaults and several other directories which in fact contains
> >>> non-editable content.  Is this planned to keep working ?
> >>
> >> The short answer is, no.  All rc.d scripts get moved to the src of the program they start.
> >>
> >> That said, if there is a big need for this, we can see about options to keep them working.
> >>
> >> What are you trying to accomplish when you do this?  Just verify the rc.d scripts match your src tree?
> > 
> > I avoid mergemaster/etcupdate and whatever else. rc.d and /etc/rc,
> > /etc/rc.subr /etc/rc.network are not suitable to etc, they are binaries
> > provided by the project not for the user editing.
> > 
> > When upgrading the host, esp. on HEAD, i usually refresh scripts by this
> > procedure and avoid any editing and implied conflict resolution for real
> > configs.
> > 
> > Not being able to easily install clean copies of these scripts would
> > be very inconvenient and time consuming.
> 
> I found that "mergemaster -iFUP" deals with unchanged files including mentioned rc* scripts just fine.
> That is, it automatically refreshes unchanged files without any silly questions just for change of $FreeBSD$.

No, you missed the point.  Whatever nice is the handling of unchanged files,
use of mergemaster forces me to handle changed files, which is exactly
what I do not want/need to do.  Yes, I update crashboxes very often, and
I want to get all new code, including the startup scripts, when I update.