Re: RFC v3: adding a temporary, non-BC gauranteed, 'private' library (was RFC v2)

2009-05-06 Thread Cornelius Schumacher
On Tuesday 05 May 2009 12:05:46 Thiago Macieira wrote: Here's the idea: - we create kdelibs/experimental in trunk/KDE yes, it's a subdir of kdelibs - however, when packaging, the KDE release team will have to split it up: kdelibs-4.x.y.tar.gz kdelibs-experimental-4.x.y.tar.gz

Re: RFC v3: adding a temporary, non-BC gauranteed, 'private' library (was RFC v2)

2009-05-06 Thread Dirk Mueller
On Tuesday 05 May 2009, Till Adam wrote: For what it's worth, and since I raised a medium size stink about this on IRC this morning, I think this is a good solution, and one that makes our (for various values of our) lives much easier than the initially suggested extragear/libs way. Thanks

Re: RFC v3: adding a temporary, non-BC gauranteed, 'private' library (was RFC v2)

2009-05-05 Thread Aaron J. Seigo
On Tuesday 05 May 2009, Thiago Macieira wrote: To all parties involved: is this acceptable? Especially note the release team, due to this requiring their work. it works for me. in this particular instance we'll be putting one more requirement down: only apps in kde's main modules can use

Re: RFC v3: adding a temporary, non-BC gauranteed, 'private' library (was RFC v2)

2009-05-05 Thread Till Adam
On Tuesday 05 May 2009 12:05:46 Thiago Macieira wrote: To all parties involved: is this acceptable? Especially note the release team, due to this requiring their work. For what it's worth, and since I raised a medium size stink about this on IRC this morning, I think this is a good solution,