Re: [cmake-developers] Making kwsys a proper library

2015-08-21 Thread David Cole via cmake-developers
Honestly, KWSys has always seemed like a boost-avoidance mechanism from an outsider's perspective. Perhaps it should be replaced with boost equivalents in projects that need to be packaged for Fedora. I assume all the boost libraries are already packaged/available. Fuel for the fire, ;-) D

Re: [cmake-developers] Making kwsys a proper library

2015-08-21 Thread Brad King
On 08/20/2015 10:19 PM, Orion Poplawski wrote: The consensus of the FPC is that the current situation with KWSys is very undesirable. While this approach may have been reasonable years ago with few consumers, it does not seem acceptable at this point. FWIW, the origin of this is the

Re: [cmake-developers] Making kwsys a proper library

2015-08-21 Thread Brad King
On 08/21/2015 10:58 AM, Ben Boeckel wrote: CMake would have to ship with multiple versions of Boost, each subsetted and likely patched. That is hardly better. This falls under the category of third-party libraries that are candidates for use in the already-proposed cleanup of KWSys: On

Re: [cmake-developers] Making kwsys a proper library

2015-08-21 Thread Ben Boeckel
On Fri, Aug 21, 2015 at 10:35:58 -0400, David Cole via cmake-developers wrote: Honestly, KWSys has always seemed like a boost-avoidance mechanism from an outsider's perspective. Perhaps it should be replaced with boost equivalents in projects that need to be packaged for Fedora. I assume all

Re: [cmake-developers] Making kwsys a proper library

2015-08-20 Thread Orion Poplawski
On 08/17/2015 09:52 AM, Brad King wrote: On 08/15/2015 12:20 AM, Orion Poplawski wrote: What makes the kwsys code special in a way that makes creating a shared library inappropriate? We want to share the code across projects but we don't want it to get in the way of those projects evolving or

Re: [cmake-developers] Making kwsys a proper library

2015-08-17 Thread Brad King
On 08/15/2015 12:20 AM, Orion Poplawski wrote: What makes the kwsys code special in a way that makes creating a shared library inappropriate? We want to share the code across projects but we don't want it to get in the way of those projects evolving or releasing. KWSys has no version number

Re: [cmake-developers] Making kwsys a proper library

2015-08-14 Thread Brad King
On 08/13/2015 10:36 PM, Orion Poplawski wrote: There is concern in Fedora that the kwsys code has become too large to be an acceptable copylib. However, as cmake is constructed at the moment it would be a huge undertaking for the Fedora packagers (mostly me) to remove it downstream. So

Re: [cmake-developers] Making kwsys a proper library

2015-08-14 Thread Ben Boeckel
On Thu, Aug 13, 2015 at 20:36:55 -0600, Orion Poplawski wrote: There is concern in Fedora that the kwsys code has become too large to be an acceptable copylib. However, as cmake is constructed at the moment it would be a huge undertaking for the Fedora packagers (mostly me) to remove it

Re: [cmake-developers] Making kwsys a proper library

2015-08-14 Thread Orion Poplawski
On 08/14/2015 08:27 AM, Ben Boeckel wrote: On Thu, Aug 13, 2015 at 20:36:55 -0600, Orion Poplawski wrote: There is concern in Fedora that the kwsys code has become too large to be an acceptable copylib. However, as cmake is constructed at the moment it would be a huge undertaking for the

[cmake-developers] Making kwsys a proper library

2015-08-13 Thread Orion Poplawski
There is concern in Fedora that the kwsys code has become too large to be an acceptable copylib. However, as cmake is constructed at the moment it would be a huge undertaking for the Fedora packagers (mostly me) to remove it downstream. So I'm asking if there is any support upstream for