Re: [OM Cooker] desktop-common-data soft dir

Per Øyvind Karlsen <[email protected]> Tue, 30 Jul 2013 20:40:30 +0200
Newsgroups gmane.linux.mandrake.cooker.devel,gmane.linux.openmandriva.cooker.devel
Message-ID <CA+0WU1SRTTrY7uC1uNspqaKENgxiXc4OCNtuRYD2cjwdU8xv7w@mail.gmail.com>
2013/7/30 Jochen Schönfelder <[email protected]>

> On Tue, 30 Jul 2013 10:55:22 -0600
> Matthew Dawkins <[email protected]> wrote:
>
> > > No point in creating separate branches of everything under moondrake/*
> > > when I'm the one who's the main maintainer of everything under  there
> and
> > > what is to be consdered as upstream.
> nope.
>
> Upstream is depending on the package. For some it's Mageia, for others it's
> ourselves, ...

Which for all of the packages in question are the repos that I'm using.

I'm not sure of what packages you refer to that has Mageia as upstream, I
have myself been the one maintaining all of these for the past couple of
years.


> Don't think we're going to split this up or change that, again. I think
> that
> we're all happy to join forces where possible, but there really is no
> reason in
> why to have the moondrake repo for half of the things and omv_software for
> the
> rest.

And since I've imported everything to one place already and is doing the
wast majority of all the maintenance work, there's no sense in forking
stuff into separate repos just to satisfy someone's obsession over naming.

Also you most possibly will strongly disagree when we change default
> configs and artwork for omv.

No, you don't change the default for everyone, you change the default for
whatever flavour that you want to maintain.
Everything related to this has support for multiple without the need for
separate repos or anything, everything can go into one master branch,
unless anyone has some specific need for other trees for their work that's
not suitable to go "upstream".

--
Regards,
Per Øyvind