Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Feb 2020 10:08:14 -0600
From:      Kyle Evans <kevans@freebsd.org>
To:        Shawn Webb <shawn.webb@hardenedbsd.org>
Cc:        "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
Subject:   Re: Return of config files to ^/etc
Message-ID:  <CACNAnaH66TNTYB_0BvRhcpDwC8f=OUycwb9=kuqvr2QVRNOqLg@mail.gmail.com>
In-Reply-To: <20200215151302.z7tcf6ipzruean7u@mutt-hbsd>
References:  <CACNAnaE5kUuJiDOHtJSE357iiFrA2JQbNuEyLh5yZgU98X_t2g@mail.gmail.com> <20200215151302.z7tcf6ipzruean7u@mutt-hbsd>

index | next in thread | previous in thread | raw e-mail

On Sat, Feb 15, 2020 at 9:13 AM Shawn Webb <shawn.webb@hardenedbsd.org> wrote:
>
> Hey Kyle,
>
> On Fri, Feb 14, 2020 at 04:42:15PM -0600, Kyle Evans wrote:
> > Hello,
> >
> > I've organized a review[0] to return most config files back to etc/.
> > Many people were concerned about the mass exodus of etc/, and many
> > have expressed a desire (privately or otherwise) for these files to
> > return- some of these folks represent downstreams or consumer projects
> > that went through the painful move the first time and would happily go
> > through the pain again to restore the status quo.
> >
> > This does mean that we'd end up with a structure that's not compatible
> > with stable/12, but is compatible with every branch before it.
> >
> > If you have an opinion for or against. please speak up now. I'd like
> > to make sure we're moving in the correct direction as a developer
> > community.
>
> I'm curious how long downstream projects would need to support both
> paradigms.
>

The answer for both downstreams and us is "however long stable/12 is
supported" for that particular project.

Something that I've intentionally not pitched yet (to avoid conflating
major issues) is the possibility of MFC'ing the move back to
stable/12. It's feasible, but requires more care and attention than it
does in head/. IIRC, when you attempt to merge an svn mv/cp to another
branch, svn will stage it as a copy from the version in head/ that
lives at the destination. So, when you try to MFC a mv/cp, you're
effectively MFC'ing all changes before it unless you take care to
assess and, as needed, revert those in the final diff.

I will volunteer to do this work if the move back happens, but I will
raise that as a follow-up issue. I suspect that it will be desired if
we do the move in head, to ease the pain of merging back to our most
recent branch.

Thanks,

Kyle Evans


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaH66TNTYB_0BvRhcpDwC8f=OUycwb9=kuqvr2QVRNOqLg>