Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 06 Jun 2018 12:18:00 -0700
From:      Cy Schubert <Cy.Schubert@cschubert.com>
To:        Brad Davis <brd@FreeBSD.org>
Cc:        Konstantin Belousov <kostikbel@gmail.com>, Eugene Grosbein <eugen@grosbein.net>, Alexander Leidinger <Alexander@leidinger.net>, rgrimes@freebsd.org, Kyle Evans <kevans@freebsd.org>, "src-committers" <src-committers@freebsd.org>, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r334617 - in head: . etc
Message-ID:  <201806061918.w56JI0kk045200@slippy.cwsent.com>
In-Reply-To: Message from Brad Davis <brd@FreeBSD.org> of "Tue, 05 Jun 2018 14:44:49 -0600." <1528231489.2440725.1397620864.5987B9ED@webmail.messagingengine.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In message <1528231489.2440725.1397620864.5987B9ED@webmail.messagingengi
ne.com>
, Brad Davis writes:
> This is a multi-part message in MIME format.
>
> --_----------=_152823148924407253
> Content-Transfer-Encoding: 7bit
> Content-Type: text/plain; charset="utf-8"
>
>
> On Tue, Jun 5, 2018, at 1:28 PM, Konstantin Belousov wrote:
> > 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 workin
> g ?
> > > >>
> > > >> 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 resol
> ution
> > > > 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 r
> efreshes 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, whi
> ch 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.
> The startup scripts will be installed as part of installworld.

Shouldn't this be worked out in a phab review first?


-- 
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  http://www.FreeBSD.org

	The need of the many outweighs the greed of the few.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201806061918.w56JI0kk045200>