[maemo-developers] Autobuilder repository priority ?

[From: Jeremiah Foster]

On Nov 3, 2009, at 1:17, Attila Csipa wrote:

> A bit short on time, so could not reply to many good posts, but  
> would not like
> to drop out of the discussion...

This is a very important discussion I feel, you have raised some  
important issues and there has been some insightful feedback from  
people like Ed Bartosh who really know the build toolchain well.

>
> On Monday 02 November 2009 23:24:12 Jeremiah Foster wrote:
>>> Attila  was asking us to solve problem with updates. And he proposed
>>> good solution. Shell we implement it right now or you propose to  
>>> wait
>>> until we have Maemo distro and all this great things?
>>
>> No, let's try and solve his proposal now. I am open to whatever  
>> people
>> think is best, I don't want to stand in the way of a new repository  
>> if
>> others think it is the right path to choose.
>
> Just to clarify things a bit - the additional repo was a suggested  
> solution to
> deeper problem(s) of overlapping repositories and fixed devel- 
> testing-extras
> promotion path. I'd much rather have those solved at the origin  
> (cleanly
> separated SDK/extras and ways to update them without one polluting  
> the other),

Yes. As I see it, this might be the core of the problem: overlapping  
repositories preventing package promotion.  For example, if python2.5- 
dbus is a 'depends', you cannot build the package for Extras.

Am I understanding this correctly?

Can you use another dependency to get the same functionality?
Can you declare in your control file that a specific version of  
python2.5-dbus be used?
Can we change the conflict that is preventing python2.5-dbus from  
being used?

My hunch is that there may be a way to solve this specific case with  
the tools we now have. If we can't we have to look at how we fix it  
and like Graham says we may be able to find our own path and maybe an  
update repository is the way to go.

Jeremiah