svn commit: r334617 - in head: . etc

[Brad Davis]

On Wed, Jun 6, 2018, at 2:25 AM, Stefan Esser wrote:
> Am 05.06.18 um 22:43 schrieb Brad Davis:
> > 
> > On Tue, Jun 5, 2018, at 1:07 PM, Renato Botelho wrote:
> >> On 05/06/18 15:26, Konstantin Belousov wrote:
> >> > On Tue, Jun 05, 2018 at 12:13:05PM -0600, Brad Davis wrote:
> >> >> On Tue, Jun 5, 2018, at 10:46 AM, 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.
> >>
> >> If I understood what Brad is saying, each rc.d script will be installed
> >> by the application it belongs to. So when it's installing SSH it will
> >> also install /etc/rc.d/sshd and you will not need to deal with rc.d
> >> files on mergemaster anymore.
> >>
> >> Is it correct, Brad?
> > 
> > Correct.
> I have for a long time (decades?) applied local changes to files in src/etc
> which (very seldom) may need a conflict resolution, and which make sure that
> /etc is populated with files that match my needs.
> 
> It is easy to change a file in /etc until it works as desired and then copy
> it to src/etc, where it is subject to updating via SVN, but still reflects
> my preferences.
> 
> With the move to source directories it will be necessary to modify rc files
> and other configuration file defaults (e.g. ttys) in a number of places.
> 
> E.g., mergemaster will try to remove the shells installed from ports from
> /etc/shells on each run and quite a number of other files will either never
> be automatically updated (by excluding them from mergemaster runs) or on
> every invocation of mergemaster, unless patched in their respective source
> directories spread over the whole source tree.
> 
> This is a BIG step backwards from my PoV, since src/etc currently is the
> equivalent of FreeBSD's concept of using /etc/rc.conf for configuration of
> all applicable system settings. Having sources of all files that are going
> to be installed in /etc (when a new system is setup or by mergemaster) is
> equivalent in the sense that the location where changes have to be applied
> is confined to just one directory, src/etc (and a few architecture dependent
> sub-directories).

You should really consider moving to etcupdate, as it uses 3-way merge and make this much easier.


Regards,
Brad Davis