[maemo-developers] where might this old version be coming from

[From: Eero Tamminen]

Hi,

ext Frank Banul wrote:
> On Wed, Oct 1, 2008 at 3:38 PM, Ryan Abel <rabelg5 at gmail.com> wrote:
>>>>> Then when I'm finally satisfied,
>>>>> promote to extras. But it seems that extras-devel has many of
>>>>> the same rules as extras. Oh well, I appreciate the information.
>>>>>
>>>> Extras-devel is a testing area, and potentially testers and developers
>>>> can install packages from there for testing, right? If developer would
>>>> reupload package with the same version how people, who install this
>>>> package from extras-devel would know which package they installed? How
>>>> they can be sure that they installed fixed package, if fixed and broken
>>>> packages would have the same version?
>>> Well I control that don't I? If I want to make sure users get the
>>> update, then I bump the revision. If I don't care, then I don't. I had
>>> the impression using extras-devel was risky anyway. Adding the risk of
>>> different code with the same revision doesn't bother me until it
>>> happens in the extras repository. All just my opinion.
>> It's wise to follow proper packaging procedure even during testing phases.
>> Two different packages with the exact same version doesn't make much sense,
>> does it? :)
> 
> If that's not a rhetorical question, yes it did make perfect sense (to
> me). My testing follows something like this. 1) Test on scratchbox
> until happy. 2) Copy the deb over to my tablet. Test again until
> happy. 3) Upload to the autobuilder, download from extras-devel on a
> 2nd tablet and test until happy. 4) Promote to extras. At this point,
> any changes (in my opinion) deserve a revision.

I don't have any idea whether Application Manager supports what I 
suggest below, but I think it's at least worth considering.

There could be a script that creates a repository from given packages,
under given directory. Repository meaning =
- certain directory structure where it puts the packages and
- "Packages" file listing the given packages

This script could be run on desktop so that one gives it the packages
one wants to test and as a directory, the USB mountpoint for the device
memory card.

At the end the script could spit out a repository URL which needs
to be added to the Application manager (something like
file:///media/mmc1/repository/).


This would allow testing package installation from a "repository"
with AM (to verify that AM handles dependencies OK, package is in
correct category, icon shows etc) without involving the extras(-devel).


I think this could be a part of the SDK.  Marius, any comments
on the feasibility of this (AM support etc)?


> In this specific case I got fed up with a gtk file chooser and
> switched to a hildon file chooser while in step 3. Is that worthy of a
> revision to something in a devel repository? I had not thought so.
> 
> But no matter, I don't have a problem with it.


	- Eero