Re: Conflicts due to renamed KDE4 ports

Am 17.04.18 um 20:29 schrieb Tobias C. Berner: > 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

Re: Conflicts due to renamed KDE4 ports

On 17/04/2018 09:11, Tijl Coosemans wrote: On Tue, 17 Apr 2018 00:42:48 +0200 Adriaan de Groot wrote: [where did this discussion take place, earlier? this is the first I've seen it] So, there are roughly two migration paths: supposing someone has x11/kde4 installed, which

Re: Conflicts due to renamed KDE4 ports

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

Re: Conflicts due to renamed KDE4 ports

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 > -

Re: Conflicts due to renamed KDE4 ports

On 17 April 2018 at 14:00, Andriy Gapon 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

Re: Conflicts due to renamed KDE4 ports

On Tue, 17 Apr 2018 00:42:48 +0200 Adriaan de Groot wrote: > [where did this discussion take place, earlier? this is the first I've seen > it] > > So, there are roughly two migration paths: supposing someone has x11/kde4 > installed, which has dependencies on many

Re: Conflicts due to renamed KDE4 ports

[where did this discussion take place, earlier? this is the first I've seen it -- oh, the ports@ list] 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

Re: Conflicts due to renamed KDE4 ports

Am 17.04.18 um 00:42 schrieb Adriaan de Groot: > [where did this discussion take place, earlier? this is the first I've seen > it] Hi Adrian, I did not see this being discussed before, just my posts that explain, why portmaster cannopt deal with the simultanous renaming of ports and packages

Re: Conflicts due to renamed KDE4 ports

Am 16.04.18 um 21:13 schrieb Tijl Coosemans: > On Mon, 16 Apr 2018 20:11:33 +0200 Stefan Esser wrote: >> When not even pkg can deal with this situation, how should portmaster? >> >> The packages are built without consideration for the requirements of a >> running system, and pkg

Re: Conflicts due to renamed KDE4 ports

On Mon, 16 Apr 2018 20:11:33 +0200 Stefan Esser wrote: > Am 16.04.18 um 12:38 schrieb Tijl Coosemans: >> On Sat, 14 Apr 2018 14:18:22 +0200 Stefan Esser wrote: >>> The way the new KDE5/KF5 ports have been introduced a few weeks back has >>> caused me quite

Re: Conflicts due to renamed KDE4 ports

Am 16.04.18 um 12:38 schrieb Tijl Coosemans: > On Sat, 14 Apr 2018 14:18:22 +0200 Stefan Esser 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

Re: Conflicts due to renamed KDE4 ports

On Sat, 14 Apr 2018 14:18:22 +0200 Stefan Esser 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 >

Re: Conflicts due to renamed KDE4 ports

On Sat, 14 Apr 2018 19:53:49 +0200, Stefan Esser stated: >Yes, but I put literally hundreds of hours of effort into >understanding portmaster (which is one monolythic 4000 line >shell script with global state that recursively invokes itself >to implement local state, with hundreds of instances

Re: Conflicts due to renamed KDE4 ports

Am 14.04.18 um 18:57 schrieb Steve Kargl: > On Sat, Apr 14, 2018 at 02:30:09PM +, Carmel NY wrote: >> On Sat, 14 Apr 2018 14:18:22 +0200, Stefan Esser stated: >> >> {truncated} >> >>> This is another case (after the implementation of FLAVOR support that does >>> not seem well-designed and

Re: Conflicts due to renamed KDE4 ports

On Sat, Apr 14, 2018 at 10:12 AM, Carmel NY wrote: > On Sat, 14 Apr 2018 09:57:07 -0700, Steve Kargl stated: > > >This discussion occurred with the introduction of FLAVORS, > >which broken all ports management tools except poudriere. > > So, you have not tried "synth" and

Re: Conflicts due to renamed KDE4 ports

On Sat, 14 Apr 2018 09:57:07 -0700, Steve Kargl stated: >This discussion occurred with the introduction of FLAVORS, >which broken all ports management tools except poudriere. So, you have not tried "synth" and I assume poudriere. -- Carmel ___

Re: Conflicts due to renamed KDE4 ports

On Sat, Apr 14, 2018 at 02:30:09PM +, Carmel NY wrote: > On Sat, 14 Apr 2018 14:18:22 +0200, Stefan Esser stated: > > {truncated} > > >This is another case (after the implementation of FLAVOR support that does > >not seem well-designed and causes lots of effort and inefficiencies in port >

Re: Conflicts due to renamed KDE4 ports

On 14/04/2018 12:18, Stefan Esser wrote: [cut] This is another case (after the implementation of FLAVOR support that does not seem well-designed and causes lots of effort and inefficiencies in port management tools like portmaster), which makes me consider giving up my efforts to keep

Re: Conflicts due to renamed KDE4 ports

On Sat, 14 Apr 2018 14:18:22 +0200, Stefan Esser stated: {truncated} >This is another case (after the implementation of FLAVOR support that does >not seem well-designed and causes lots of effort and inefficiencies in port >management tools like portmaster), which makes me consider giving up my