RFC v3: adding a temporary, non-BC gauranteed, 'private' library (was RFC v2)
Thiago Macieira <
thiago@...>
2009-05-05 10:05:46 GMT
Em Terça-feira 05 Maio 2009, às 10:49:38, Thiago Macieira escreveu:
> Em Terça-feira 05 Maio 2009, às 09:10:24, Kevin Ottens escreveu:
> > On Tuesday 5 May 2009 09:03:51 Kevin Ottens wrote:
> > > I honestly far prefer a trunk/KDE/kdelibs-experimental over
> > > trunk/extragear/libs.
> >
> > Oh, and to make it clear, I even prefer kdelibs/experimental to both
> > other solutions even if it puts some more work on the packagers
> > initially.
>
> No, it's not. It has to be OUTSIDE kdelibs.
Uh... sorry for the harsh email. I misread your email anyways. (Of course I
can't tell you what your opinion is or isn't :->)
Anyways, after another heated discussion on IRC we reached a different
compromise.
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
the latter contains *only* the experimental subdir; the former contains
everything else, except the experimental dir
- recommendation: add -DKDELIBS_NO_EXPERIMENTAL to kdelibs to check if
building without the experimental bits works
- constraints:
* kdelibs-experimental-4.x.y.tar.gz MUST build alone (outside of kdelibs)
(Continue reading)