Date: Tue, 17 Apr 2018 16:19:39 +0200 From: "Tobias C. Berner" <tcberner@freebsd.org> To: Andriy Gapon <avg@freebsd.org> Cc: Adriaan de Groot <adridg@freebsd.org>, "kde@FreeBSD.org" <kde@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: Conflicts due to renamed KDE4 ports Message-ID: <CAOshKte2mrETdLA71v0NVQ2KR8UgAy4xZvksihPeeLX0W4mw2A@mail.gmail.com> In-Reply-To: <1172371d-ce51-d13b-b421-ff06363ac49e@FreeBSD.org> References: <a9ce1576-a254-4e79-3e50-b90d49827a1e@freebsd.org> <b3297fd4-05a4-f824-4fdd-21227531fc57@freebsd.org> <20180416211329.52e4c0dc@kalimero.tijl.coosemans.org> <18601817.syqV60Bg9A@beastie.bionicmutton.org> <1172371d-ce51-d13b-b421-ff06363ac49e@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 April 2018 at 14:00, Andriy Gapon <avg@freebsd.org> wrote: > On 17/04/2018 10:24, Adriaan de Groot wrote: > > So, there are roughly two migration paths: supposing someone has > x11/kde4 > > installed, which has dependencies on many applications and a Plasma 4 > desktop, > > kde@ wants (wanted) to make it possible to migrate to a still-KDE4 > desktop, > > while renaming everything to have a -kde4 suffix. The other path is to > migrate > > to the latest-and-greatest-from-KDE .. we don't have a metaport for > that, and > > if we do get one it probably won't be called x11/kde5. > > > > For single applications, the migration looks similar: you had, around > january > > 2018, port <foo>. That's the KDE4 version. Now there is port <foo>-kde4, > if > > you want to stick to KDE4 software (which is no longer released > upstream, and > > is based on an EOL toolkit, but some people feel quite strongly about > this). > > Ports <foo> are returning, without a suffix, to mean "the > latest-and-greatest- > > version-of-<foo>". This is consistent with other ports which have a > <foo>, > > sometimes a <foo>-devel for upcoming things, and a <foo>-<version> for > older > > versions if you have specific dependencies on old versions. > > > > Historically, things were a mess with naming with the KDE ports. We > think > > we've got a good scheme now: <foo>-kde4 (and in the far future, > <foo>-kf5) for > > versions of the software based on an older stack, and <foo> for the > current > > one. But the pain of getting from the mess to something better organized > has > > to happen at some point. > > Moin moin I am just curious why not have explicit -kde4 and -kde5. > I think that qt sets a good example and there is no confusion and no > migration > Short answer: Because there is no kde5 Long answer: KDE is shipped in mulitple, let's call them groups: - frameworks (libraries to build kde and qt applications) -- we call these ports kf5-foo - plasma (the desktop) -- we'll call these ports plasma5-foo - applications (the applications) Now, previously during KDE SC4 days, this was a whole "blob". This is why it made sense to call them all kde4-foo or foo-kde4. Now with this new split there is no real notion to call an application foo-kde5. For example during the transition in the last few years many KDE Application releases were a mix of Qt4 and Qt5 (i.e. kdelibs4 and kf5 based applications). So we would have had a kate-kde5 that was using kdelibs-kde4 ... well that would have been confusing too. The same thing will eventually happen when the next KDE Frameworks will roll around I expect, where the applications get updated one after another, with mixed releases in between. We opted for the same method as other ports use. A new version appears that is incompatible, move "bar/foo" to "bar/foo3" and update "bar/foo" in place. This is not a new thing, it's just a lot in one go, I agree, and I'm sorry for the inconvenience. However, let's not make a problem, that could essentially be solved by a pkg-delete followed by a pkg-add too complicated :) I'll try to create a shell script to rewire the pkg's automatically to the new origin... mfg Tobias pain in the future when 6 appears. > > -- > Andriy Gapon >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOshKte2mrETdLA71v0NVQ2KR8UgAy4xZvksihPeeLX0W4mw2A>