From owner-freebsd-ports@freebsd.org Tue Apr 17 18:29:38 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B2A7F904D4 for ; Tue, 17 Apr 2018 18:29:38 +0000 (UTC) (envelope-from tcberner@gmail.com) Received: from mail-qt0-f174.google.com (mail-qt0-f174.google.com [209.85.216.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A05B37598A; Tue, 17 Apr 2018 18:29:37 +0000 (UTC) (envelope-from tcberner@gmail.com) Received: by mail-qt0-f174.google.com with SMTP id s2so19807026qti.2; Tue, 17 Apr 2018 11:29:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ct1HdW43YWGo4SyvZgJ6ULZ5KZfyceJ36vIopF82rzs=; b=Sh9SZhL9G0rnWVibQUrUK4cMBebyr76oDC6wX6paXeEDu9fBcrJOViJS6IYSjJVQxc Mp9SbNabLX1CRkMtdlW8pDzGIEBfCvt51C2PPt56h5pKb+skdPB1M11VZgJzNnL4ywbF Qye2wRjCqEyK7sYVnNooBM3OxS0fLtRoVnQmDoDszv0XZDTygzVlBY8SZnQcN3Skt1Lg m1Qp4zg+3+9ahbPkSbbLGiueqmRECgXYRBHAurlnwLWfXa0D3/wE4yBvpxyb/CNYtUPe 4Kictq274xCst8h2kILjlAv/bollVQCIIuX6S9u7d3Z3o5NbfWDIfjDM/UcUxkXXKQ95 Zj2g== X-Gm-Message-State: ALQs6tAT7acSa+gm3jqY5K0udhNu1pAbwdV4Xzb/SOerk6Qukd2Guazv bOoSklPNH3HQVJgDcy2vupPElXPK X-Google-Smtp-Source: AIpwx4+c3KOZ/sv8wxBAE6JhVpNDs7hV4liAkfHPXGH4A4/UHNnZLcfWrwmBzg1GuLxvlF61P3/7cw== X-Received: by 10.200.82.130 with SMTP id s2mr3330106qtn.284.1523989777025; Tue, 17 Apr 2018 11:29:37 -0700 (PDT) Received: from mail-qk0-f182.google.com (mail-qk0-f182.google.com. [209.85.220.182]) by smtp.gmail.com with ESMTPSA id e64sm10964862qka.18.2018.04.17.11.29.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Apr 2018 11:29:36 -0700 (PDT) Received: by mail-qk0-f182.google.com with SMTP id s70so5750281qks.13; Tue, 17 Apr 2018 11:29:36 -0700 (PDT) X-Received: by 10.55.19.149 with SMTP id 21mr3223679qkt.253.1523989776347; Tue, 17 Apr 2018 11:29:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.62.182 with HTTP; Tue, 17 Apr 2018 11:29:35 -0700 (PDT) In-Reply-To: <20180417174352.797247c9@kalimero.tijl.coosemans.org> References: <20180416211329.52e4c0dc@kalimero.tijl.coosemans.org> <18601817.syqV60Bg9A@beastie.bionicmutton.org> <1172371d-ce51-d13b-b421-ff06363ac49e@FreeBSD.org> <20180417174352.797247c9@kalimero.tijl.coosemans.org> From: "Tobias C. Berner" Date: Tue, 17 Apr 2018 20:29:35 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Conflicts due to renamed KDE4 ports To: Stefan Esser Cc: "Tobias C. Berner" , Andriy Gapon , "kde@FreeBSD.org" , Adriaan de Groot , freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2018 18:29:38 -0000 Moin moin Here's a script which should automatically fix the origin for the kde4-versioned ports (based on the MOVED entries of r465345): http://people.freebsd.org/~tcberner/scripts/fix_kde4_origins.sh It //should// set the origins properly for the moved ports, and the output should be on the lines of # ./fix_kde4_origins.sh [...] - sysutils/baloo-widgets [sysutils/baloo-widgets-kde4] is not installed. + Changing origin of nepomuk-core-4.14.3_14 from sysutils/nepomuk-core to sysutils/nepomuk-core-kde4. - sysutils/kfloppy [sysutils/kfloppy-kde4] is not installed. - sysutils/ksystemlog [sysutils/ksystemlog-kde4] is not installed. + Changing origin of baloo-4.14.3_5 from sysutils/baloo to sysutils/baloo-kde4. + Changing origin of kfilemetadata-4.14.3_13 from sysutils/kfilemetadata to sysutils/kfilemetadata-kde4. [...] Please let me know if that works for you, or how I could improve it. mfg Tobias On 17 April 2018 at 17:43, Tijl Coosemans wrote: > On Tue, 17 Apr 2018 16:19:39 +0200 Tobias C. Berner wrote: > > 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. > > I don't think this is the norm. All the big ports (perl, python, php, > gcc, mysql, gtk, qt,...) just leave bar/foo and create bar/foo4. In > place updating to an incompatible version can be a complete surprise > for users (POLA violation) and leave them with a broken system. >