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

List:       kde-active
Subject:    Roots to branches
From:       sebas () kde ! org (Sebastian =?ISO-8859-1?Q?K=FCgler?=)
Date:       2011-06-01 21:50:15
Message-ID: 1586279.Xku0vFchk7 () marvin ! vizzzion ! net
[Download RAW message or body]

On Wednesday, June 01, 2011 23:19:23 Ivan ?uki? wrote:
> > Is it at all possible to put the additional needed bits apart from
> > kdelibs and -runtime? If not, we'll have to release Plasma Active One
> > on top of unstable kdelibs (-runtime) which is not exactly desirable...
> 
> A possible solution would be for packagers to remove the kamd and
> libkact from packages, and pack those (new versions) separately.
> 
> But, if that were to be the case, what would you do when we start
> patching apps to notify us of resources they open?
> 
> IMO, the easiest way is to branch of stable (and constantly merging
> stable into it) and just develop things that need to be developed.

Ok, sounds less complex in the end. Let's do it this way. Can we document 
somewhere which branches are needed for what, so my head doesn't explode 
everytime I update / test packages?
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9

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

Configure | About | News | Add a list | Sponsored by KoreLogic