Date: Wed, 06 Jun 2018 05:41:50 -0600 From: Brad Davis <brd@FreeBSD.org> To: Stefan Esser <se@freebsd.org>, Renato Botelho <garga.bsd@gmail.com>, Konstantin Belousov <kostikbel@gmail.com> Cc: "src-committers" <src-committers@freebsd.org>, Kyle Evans <kevans@freebsd.org>, svn-src-all@freebsd.org, rgrimes@freebsd.org, svn-src-head@freebsd.org, Alexander Leidinger <Alexander@leidinger.net> Subject: Re: svn commit: r334617 - in head: . etc Message-ID: <1528285310.3551889.1398315032.22267C9D@webmail.messagingengine.com> In-Reply-To: <f0fff0b8-11d2-796b-a290-f7492e699635@freebsd.org> References: <201806041847.w54IlCUu097084@pdx.rh.CN85.dnsmgr.net> <1528138550.3632147.1396107464.614818A8@webmail.messagingengine.com> <20180605150022.Horde.emnJxb8rKYqAvChLgWoX9vf@webmail.leidinger.net> <1528212242.2273706.1397239144.6BEBF1F9@webmail.messagingengine.com> <20180605164627.GM2450@kib.kiev.ua> <1528222385.2736229.1397446048.17853CA8@webmail.messagingengine.com> <20180605182605.GN2450@kib.kiev.ua> <ab9725b4-88a7-9af4-db5b-2886db3aed14@gmail.com> <1528231416.2440607.1397619456.294EF898@webmail.messagingengine.com> <f0fff0b8-11d2-796b-a290-f7492e699635@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 6, 2018, at 2:25 AM, Stefan Esser wrote: > Am 05.06.18 um 22:43 schrieb Brad Davis: > >=20 > > 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 cont= ains > >> >>> non-editable content.=C2=A0 Is this planned to keep working ? > >> >> > >> >> The short answer is, no.=C2=A0 All rc.d scripts get moved to the sr= c of the > > program they start. > >> >> > >> >> That said, if there is a big need for this, we can see about option= s to > > keep them working. > >> >> > >> >> What are you trying to accomplish when you do this?=C2=A0 Just veri= fy 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 binar= ies > >> > 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? > >=20 > > Correct. > I have for a long time (decades?) applied local changes to files in src/e= tc > which (very seldom) may need a conflict resolution, and which make sure t= hat > /etc is populated with files that match my needs. >=20 > It is easy to change a file in /etc until it works as desired and then co= py > it to src/etc, where it is subject to updating via SVN, but still reflects > my preferences. >=20 > With the move to source directories it will be necessary to modify rc fil= es > and other configuration file defaults (e.g. ttys) in a number of places. >=20 > 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 nev= er > 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. >=20 > 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 depend= ent > sub-directories). You should really consider moving to etcupdate, as it uses 3-way merge and = make this much easier. Regards, Brad Davis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1528285310.3551889.1398315032.22267C9D>