RFC v2: adding a temporary, non-BC gauranteed, 'private' library

Chani chanika at gmail.com
Fri Apr 24 21:27:15 BST 2009

On April 24, 2009 10:01:54 Aaron J. Seigo wrote:
> On Friday 24 April 2009, Brad Hards wrote:
> > On Friday 24 April 2009 08:10:22 pm Thiago Macieira wrote:
> > > We want to have knotificationitem-0.1.tar.gz. The place for individual
> > > packages is extragear.
> >
> > Another option would be an extended stay in review.
> i'd prefer not to muddy the purpose of kdereview (which is, well,
> reviewing)
> in terms of "playground, review, module" what i'm looking for is something
> between review and module that one might call "staging"

so make something ;)
sounds like friedrich wants that something too, so why don't you two create a 
new staging/experimental/whatever module that comes after kdelibs 
(kdepimlibs?) in the dependency chain? 

so what if it's empty after a while? it sounds like the least painful option 
here... and nobody has to worry about parts of extragear needing to be built 
earlier than others (although if nobody builds extragear in one chunk then 
maybe that doesn't matter and this experimental dir could go inside extragear 
just as easily - but it seems odd to me to have something in extragear that's 
needed to build lots of core apps. I always thought of extragear as optional.)

This message brought to you by eevil bananas and the number 3.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090424/43731fd5/attachment.sig>

More information about the kde-core-devel mailing list