30 Jul
2019
30 Jul
'19
5:53 p.m.
Hi Pete,
On Tue, 30 Jul 2019, 16:34:59 +0200, Hans-Peter Jansen wrote:
Dear Manfred, dear Richard,
Am Dienstag, 30. Juli 2019, 15:01:46 CEST schrieb Richard Brown:
Nevertheless, Thorsten still kept /usr/etc in hist list when opening the
second round ;)
To be honest, libostree has a pretty clear focus, which does not
actually cover much of what I care about, at least. OpenEmbedded sounds
great, but I doubt, there will be any relevant standard adhered to by
any of all the players outside building and selling their embedded Linux
appliances - I spent too much time talking with all of them between 1999
to 2006; everybody was listening, but nobody wanted to buy into it...
"flatpak", I don't give a shit at all! "GNOME Continuous", again,
I
don't like GNOME either...
So, to me it sounds more how much we can win building on a long
established relationship between /etc <-> /usr/etc, rather than running
discussions which may lead to nowhere... At least, we're in the second
round this time, thanks Thorsten! FWIW, I certainly can live with
/usr/config, but from where I come from, /usr/etc appears much more
appealing and well known and established.
[...]
OSTree is using /usr/etc to store data for their three-way-diff-merge
of configuration files.
On *BSD, users have to edit the files in /usr/etc, while in our case,
this should be "read-only", and user have to create the changes in /etc.
There are distributions who did the "UsrMerge" by moving /etc to
/usr/etc and makeing /etc a symlink to /usr
I don't care much about *BSD layout, but since OSTree seems an interesting
project, as well as the last point renders this approach problematic at least.
So he concludes:
What would happen if we choose /usr/etc and other
distributions cannot
follow us?
1. we are the only one who are doing, and will always be different
2. The others will come up with another standard, and either we are
alone/different, or have to do the work a second time.
I don't like any of this options.
Let me add: we should not interfere with libostree based projects (which would
make libostree based projects unfeasible for our platform, especially since
some Fedora-based projects adapt this already).
So this is enough evidence of not using /usr/etc, no matter how much we all
agree on this choice otherwise, isn't it? Cheers,
Pete
Cheers.
l8er
manfred