Re: [OS X] adding a link module to all KF5 targets

2015-09-23 Thread René J . V . Bertin
Let me just add what me me come to KDE. That was mostly out of unhappiness with changes in OS X applications and development, and to find replacements for mail and IDE applications (and because I'd seen on Linux that KDE4 was about ripe to be an alternative to the OS X GUI, I was both

Re: [OS X] adding a link module to all KF5 targets

2015-09-23 Thread Boudewijn Rempt
On Wed, 23 Sep 2015, Nicolás Alvarez wrote: 2015-09-22 19:28 GMT-03:00 Albert Astals Cid : El Dimarts, 22 de setembre de 2015, a les 23:04:22, René J.V. Bertin va escriure: On Tuesday September 22 2015 22:35:40 Albert Astals Cid wrote: > Shouldn't KF5 work with those

Re: [OS X] adding a link module to all KF5 targets

2015-09-22 Thread Albert Astals Cid
El Dimarts, 22 de setembre de 2015, a les 12:52:46, René J.V. Bertin va escriure: > Hello, > > I'm working on a Mac OS X specific patch that would require adding a small > object (probably a .o file) to the link list for *all* targets that use > KF5. This object contains some logic that flips

Re: [OS X] adding a link module to all KF5 targets

2015-09-22 Thread René J . V . Bertin
On Tuesday September 22 2015 22:35:40 Albert Astals Cid wrote: > Shouldn't KF5 work with those sandboxing? I'd expect that KF5 goal is that > you > can use it in applications that end up in the App Store. It might be possible that someone will someday write an application that uses (a) KF5

Re: [OS X] adding a link module to all KF5 targets

2015-09-22 Thread Albert Astals Cid
El Dimarts, 22 de setembre de 2015, a les 23:04:22, René J.V. Bertin va escriure: > On Tuesday September 22 2015 22:35:40 Albert Astals Cid wrote: > > Shouldn't KF5 work with those sandboxing? I'd expect that KF5 goal is that > > you can use it in applications that end up in the App Store. > >

Re: [OS X] adding a link module to all KF5 targets

2015-09-22 Thread René J . V . Bertin
Albert Astals Cid wrote: >> (just a non-default option). But it shouldn't be compulsory for everyone. > > Why not? Because it's an enormous lot of extra work that will lead to equally enormous disk overhead (duplicating everything for each and every application), as well as to applications