Information regarding upcoming Gitlab Migration: clarifications
mpyne at kde.org
Sun May 3 00:29:41 BST 2020
On Fri, May 01, 2020 at 09:25:18AM -0400, Allen Winter wrote:
> On Thursday, April 30, 2020 5:15:43 PM EDT Albert Astals Cid wrote:
> > El dijous, 30 d’abril de 2020, a les 21:31:02 CEST, Ben Cooksley va escriure:
> > > On Fri, May 1, 2020 at 6:04 AM Ivan Čukić <ivan.cukic at kde.org> wrote:
> > > >
> > > > > We have made a big fuss in the past about having different projects
> > > > > that do the same thing and now we'll have that but also we'll have
> > > > > several projects with the same name?
> > > > > It really feels off to me and I wonder if this is related to the move to
> > > > > gitlab.
> > > >
> > > > +1 to both sentiments - that projects should have different names and that
> > > > this is a bit off topic for the gitlab migration.
> > >
> > > The projects *DO* have very different names. That *HAS NOT* changed.
> > > To use the example Bhushan gave above, one is called Plasma Mobile
> > > Dialer and the other one is called Maui Dialer.
> > >
> > > With the current git.kde.org setup, we have a flat namespace, so all
> > > repositories if the name appears to be generic (as dialer is) have to
> > > be namespaced by prefixing of the repository name.
> > >
> > > With Gitlab however we will now namespaces that group repositories,
> > > making the prefixing unnecessary and as some projects have complained
> > > about, duplicative.
> > >
> > > Otherwise you end up with plasma-mobile/plasma-mobile-dialer as your
> > > path, which just looks silly.
> > Am I the only person that just has all the repos on the same folder? I thought it was the common thing to do :?
> I use kdesrc-build and I see the repos in a hierarchy.
> In particular, I like frameworks in frameworks in kdepim in kde/pim
> I don't see that I'm setting any special "layout in a hierarchy" option in my kdesrc-buildrc
So it's been a few months since we had switched the default, but since
it's clearly an invasive change, the way we addressed it was to make the
flat hierarchy a default for new users (who use either of the 'quick
config' schemes like kdesrc-build-setup or kdesrc-build
--initial-setup), but to leave the built-in default unchanged.
So in essence, existing kdesrc-build users (who had a folder-based
layout by default unless they went out of their way to find the right
option) saw no change, but new users would have that option pre-set for
them in the config.
- Michael Pyne
More information about the kde-core-devel