[maemo-developers] Diablo, do we need a separate repository?

[From: Ryan Pavlik]

Niels Breet wrote:
> On Mon, May 5, 2008 13:58, Rafael Proença wrote:
>   
>>> Do we need a separate extras repository for diablo or should we just
>>> add a link to chinook?
>>>
>>>       
>> My guess is that if you link diablo to chinook what will happen is that
>> all the chinook boxes will be upgraded to diablo, which, I think, is not
>> ideal and even not compatible even though the binaries are compatible, the
>> core system will not be (for example, I heard that the user will not have
>> to reflash the device to upgrade the distribution once they have Diablo
>> installed).
>>
>>     
>
> I think I need to clarify that I was talking about the extras repository
> here. This is about community created packages in extras.
>
> System packages would be served from a different repository.
>
>   
>> IMO, the compatibility of binary packages is not the only problem here.
>> But
>> the packages' version and are.
>>     
>   
For those working with the enhancements, it would obviously be best to 
keep the Diablo stuff separate, but allow a very easy forward/back-port 
of packages.  In many cases, it's just a changing of a target in the 
debian changelog - is there someway a web-based "backport/forwardport" 
service could be put together to allow the advantages of a separate 
repository while not inhibiting the ability to share essentially 
identical packages?

-- 
Ryan Pavlik
www.cleardefinition.com

#282  +  (442) -  [X]
A programmer started to cuss
Because getting to sleep was a fuss
As he lay there in bed
Looping 'round in his head
was: while(!asleep()) sheep++;