Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1

Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

florian commit schreef:
> prismstumbler: add 0.7.4pre1


> packages/prismstumbler/prismstumbler_0.7.4pre1.bb

That is against our versioning policy, this way you can't upgrade to 0.7.4 when it gets
released[1]. Use _0.7.3+0.7.4pre1 instead.

Regards,

Koen


[1] not without epoch support, but that's not meant to paper over bugs like this
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGD1+HMkyGM64RGpERAjFBAJ9Q8dl78nY+f/vm3YkqTnBntC9SJQCeN7Ho
VucIW14/SeQ597S2obc5t48=
=L5TC
-----END PGP SIGNATURE-----

Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1

[Øyvind Repvik]

On Sunday 01 April 2007 09:30, Koen Kooi wrote:
> florian commit schreef:
> > prismstumbler: add 0.7.4pre1
> >
> >
> > packages/prismstumbler/prismstumbler_0.7.4pre1.bb
>
> That is against our versioning policy, this way you can't upgrade to 0.7.4
> when it gets released[1]. Use _0.7.3+0.7.4pre1 instead.

A semi-related question. Where is this policy? There is apparently a bunch of 
policies that I am unaware of, and I'd like a pointer to them.

Øyvind

Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1

[Richard Purdie]

On Sun, 2007-04-01 at 11:59 +0200, Øyvind Repvik wrote:
> On Sunday 01 April 2007 09:30, Koen Kooi wrote:
> > florian commit schreef:
> > > prismstumbler: add 0.7.4pre1
> > >
> > >
> > > packages/prismstumbler/prismstumbler_0.7.4pre1.bb
> >
> > That is against our versioning policy, this way you can't upgrade to 0.7.4
> > when it gets released[1]. Use _0.7.3+0.7.4pre1 instead.
> 
> A semi-related question. Where is this policy? There is apparently a bunch of 
> policies that I am unaware of, and I'd like a pointer to them.

http://www.openembedded.org/wiki/Policies

The version policy is there at least. The aim was simply to try and
standardise things so package upgrades always work.

Cheers,

Richard

Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1

[Leon Woestenberg]

Richard et al,

On 4/1/07, Richard Purdie <rpurdie@rpsys.net> wrote:
> On Sun, 2007-04-01 at 11:59 +0200, Øyvind Repvik wrote:
> > A semi-related question. Where is this policy? There is apparently a bunch of
> > policies that I am unaware of, and I'd like a pointer to them.
>
> http://www.openembedded.org/wiki/Policies
>
> The version policy is there at least. The aim was simply to try and
> standardise things so package upgrades always work.
>

Also, I am as-of-yet clueless on the new epoch support, let alone
policy. Can someone pls add some info on this?

Thanks, regards,
-- 
Leon

Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1

[Florian Boor]

Hi,

Koen Kooi schrieb:
> That is against our versioning policy, this way you can't upgrade to 0.7.4 when it gets
> released[1]. Use _0.7.3+0.7.4pre1 instead.

I remember we had these kind of trouble with ipkg before. Wouldn't it be better
to make it possible to handle this properly? I guess we will run into this again
and again in future.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de

1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76

Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1

[Paul Sokolovsky]

Hello Florian,

Monday, April 2, 2007, 12:03:34 PM, you wrote:

> Hi,

> Koen Kooi schrieb:
>> That is against our versioning policy, this way you can't upgrade to 0.7.4 when it gets
>> released[1]. Use _0.7.3+0.7.4pre1 instead.

> I remember we had these kind of trouble with ipkg before.

  Why we and why ipkg? Any packaging system which tries to do its work
well hits into such issues. In this regard, OE follows Debian's way to
handle this. (Even though I was unable to find exact best
practices to resolve such cases, they only mumble that it should be
done: http://www.debian.org/doc/debian-policy/ch-binary.html#s-versions ;
anyway, + notation is what actually being used).

  I'm not sure how other packaging systems solve this, for example,
look at FC6 RPM pile shows that they have *pre* stuff without clearly
distinguishable pattern of handling it syntactically. But it's known
where that leads to - to inability to upgrade to a new distro release.

> Wouldn't it be better
> to make it possible to handle this properly? I guess we will run into this again
> and again in future.

> Greetings

> Florian




-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com

Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Sokolovsky schreef:

>>> That is against our versioning policy, this way you can't upgrade to 0.7.4 when it gets
>>> released[1]. Use _0.7.3+0.7.4pre1 instead.
> 
>> I remember we had these kind of trouble with ipkg before.
> 
>   Why we and why ipkg? Any packaging system which tries to do its work
> well hits into such issues. In this regard, OE follows Debian's way to
> handle this. (Even though I was unable to find exact best
> practices to resolve such cases, they only mumble that it should be
> done: http://www.debian.org/doc/debian-policy/ch-binary.html#s-versions ;
> anyway, + notation is what actually being used).
> 
>   I'm not sure how other packaging systems solve this, for example,
> look at FC6 RPM pile shows that they have *pre* stuff without clearly
> distinguishable pattern of handling it syntactically. But it's known
> where that leads to - to inability to upgrade to a new distro release.
> 
>> Wouldn't it be better
>> to make it possible to handle this properly? I guess we will run into this again
>> and again in future.

It would be best if upstream (prismstumbler in this case) would use proper versioning to
start with, but if that is not possible we can paper over it in OE.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGEikFMkyGM64RGpERAvcfAJsFp0Cez/LN84vKGUBAXnbEEAkcAACbB6Jr
MKjIaA7nMU6DhAUQ05UxilY=
=21uY
-----END PGP SIGNATURE-----

Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1

[Florian Boor]

Hi,

Koen Kooi schrieb:
> It would be best if upstream (prismstumbler in this case) would use proper versioning to
> start with, but if that is not possible we can paper over it in OE.

I do not agree... sure it might be better to have simpler versions but that's
not the point. I can change this in prismstumbler because I maintain it, but
this world is not perfect we will run into the same situation again with another
package. These "pre" versions are quite common and the documentation explains
how to handle these already so we should be able to teach our software to do the
same. That's way better then teaching users and even if it does not work in all
cases it is quite likely to be more reliable than having a guideline for it.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de

1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76

Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Florian Boor schreef:
> Hi,
> 
> Koen Kooi schrieb:
>> It would be best if upstream (prismstumbler in this case) would use proper versioning to
>> start with, but if that is not possible we can paper over it in OE.
> 
> I do not agree...

You don't agree with OE's versiong policy!?!?!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGElICMkyGM64RGpERAtIRAJoDYVBIO1SltepuUrlVZiBJJamc0wCfdOdz
LK5+/huSj+7a/HuExg5irqU=
=jVxd
-----END PGP SIGNATURE-----