All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Florian Boor <florian.boor@kernelconcepts.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1
Date: Tue, 3 Apr 2007 13:00:33 +0300	[thread overview]
Message-ID: <583221585.20070403130033@gmail.com> (raw)
In-Reply-To: <4610C6E6.30102@kernelconcepts.de>

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




  reply	other threads:[~2007-04-03 10:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1HXnn8-0007Dx-JK@linuxtogo.org>
2007-04-01  7:30 ` [oe-commits] org.oe.dev prismstumbler: add 0.7.4pre1 Koen Kooi
2007-04-01  9:59   ` Øyvind Repvik
2007-04-01 10:08     ` Richard Purdie
2007-04-01 20:42       ` Leon Woestenberg
2007-04-02  9:03   ` Florian Boor
2007-04-03 10:00     ` Paul Sokolovsky [this message]
2007-04-03 10:14       ` Koen Kooi
2007-04-03 13:02         ` Florian Boor
2007-04-03 13:09           ` Koen Kooi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=583221585.20070403130033@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=florian.boor@kernelconcepts.de \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.