RFC v2: adding a temporary, non-BC gauranteed, 'private' library
kevin.krammer at gmx.at
Fri Apr 24 21:19:52 BST 2009
On Friday, 2009-04-24, Friedrich W. H. Kossebau wrote:
> Vrendredi, le 24 avril 2009, à 21:16, Kevin Krammer a écrit:
> > As with any other external library I would just install the respective
> > development package.
> > At least I don't build all the dependencies from source when building KDE
> > from trunk.
> But knotificationitem isn't an external library. It is a wanna-be part of
> kdelibs, just not API-stable enough to be included officially currently. So
> knotificationitem-trunk depends on kdelibs-trunk. And module-trunk depends
> on knotificationitem-trunk and kdelibs-trunk. A development package might
> not be up-to-date enough (unless you mean tuesday-trunk-packages?).
Since it would be an external library, module-trunk would not depend on
knotificationitem-trunk but the most recent released version.
Just like with any other library.
> > You would only need to inject knotificationitem if for whatever reason
> > you want to build an not-yet-released version.
> ? I am talking of trunk. Here all things could change BIC on mondays, and
> dependant modules are allowed to depent on the version of the latest
> monday. So I always need uptodate packages, at least if i don't track all
> BIC changes to know if I really need to update. But I guess we lost each
> other somewhere here.
Sure, but we don't rebuild everything just because one of the external
dependencies happens to do something incompatible in the repository.
We use their releases.
We can update trunk to require new released whenever we want unless there is a
freeze on our repository. At which point we select a version we need to depend
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel