Date: Mon, 16 Apr 2018 12:38:09 +0200 From: Tijl Coosemans <tijl@FreeBSD.org> To: Stefan Esser <se@freebsd.org> Cc: Ports FreeBSD <freebsd-ports@FreeBSD.org>, FreeBSD Port-Manager <portmgr@FreeBSD.org> Subject: Re: Conflicts due to renamed KDE4 ports Message-ID: <20180416123809.49c44527@kalimero.tijl.coosemans.org> In-Reply-To: <a9ce1576-a254-4e79-3e50-b90d49827a1e@freebsd.org> References: <a9ce1576-a254-4e79-3e50-b90d49827a1e@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 14 Apr 2018 14:18:22 +0200 Stefan Esser <se@freebsd.org> wrote: > The way the new KDE5/KF5 ports have been introduced a few weeks back has > caused me quite some effort (more than 100 hours of work), and now there > have been further changes to implement KDE5 support (which I generally > appreciate), which cause further complications and seem not to be well > thought out. > > These problems affect at least all portmaster users, but I guess portupgrade > is affected as well and a "pkg upgrade" dry-run indicates, that it will also > cause breakage to binary upgrades of KDE4 installations. Removing entries from MOVED after only a few weeks is a bad idea, but it's not something you have to worry about. As long as portmaster behaves more or less the same as pkg you're good.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180416123809.49c44527>