On Fri, 20.02.15 11:07, Dennis Gilmore (dennis(a)ausil.us) wrote:
On Fri, 20 Feb 2015 11:04:13 -0600
Dennis Gilmore <dennis(a)ausil.us> wrote:
> On Fri, 20 Feb 2015 17:36:17 +0100
> Lennart Poettering <mzerqung(a)0pointer.de> wrote:
>
> > On Fri, 20.02.15 16:24, Peter Robinson (pbrobinson(a)gmail.com) wrote:
> >
> > > >> > Sorry for the inconvenience and feel free to add bugs to
the
> > > >> > tracker, which are caused by systemd changes and have to be
> > > >> > fixed in other components.
> > > >>
> > > >> Are you going to start notifying deve@ of upcoming changes that
> > > >> may impact other areas of the distro too rather than just land
> > > >> them without notification or discussion?
> > > >
> > > > Oh god, stop this, will you?
> > >
> > > No, I mean the above in general for general changes you make that
> > > affect the distro as a whole. You generally land them without
> > > notification.
> >
> > I "generally" do that? Can you be more precise?
>
> A recent example, systemd decided that os-release needed to be moved
> to /usr/lib/ I did not see any notification on devel@ nor was i
> contacted directly. the first I heard of it was a third party person
> filing a bug against fedora-release
I should add that changing it broke the compose process and was quickly
fixed. wider communication means that other effected components have
some visibility into things that may effect them.
You cannot really blame me for breakages for things I neither asked
for nor was involved with at all in Fedora.
Lennart
--
Lennart Poettering, Red Hat