[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: RFC v2: adding a temporary, non-BC gauranteed, 'private' library
From:       Chani <chanika () gmail ! com>
Date:       2009-04-24 20:27:15
Message-ID: 200904241327.27509.chanika () gmail ! com
[Download RAW message or body]


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.
www.chani3.com

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]