On Wed, Oct 1, 2008 at 12:04 PM,  <[EMAIL PROTECTED]> wrote:
>>I'm sorry. I thought extras-devel was a testing area of sorts.
>>Upload something try it out, see how it goes. Then tweak and
>>go through the process again.
> You're right. We just have different definition of tweak :)
> From my point of view any code change has to reflect package revision if
> package uploaded to the repository.
>
> The reason of the problem you described is buggy repository management
> software. However, it doesn't mean that reuploading the same version of
> package is a good practice. That's why we're going to implement version
> check for packages uploaded to the build to avoid this. If you disagree,
> please speak up.

I don't have any problem with it. I just need to understand and act accordingly.

>> 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.

Frank
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Reply via email to