From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] ptxdist-2011.01.0 bug in make ipkg-push
Date: Thu, 8 Dec 2011 10:45:00 -0500 [thread overview]
Message-ID: <CAMwGMjzuoxO4LNaiei1-52LAa4kDj_1Lb_1Sf+YjJ1CDXCZHuA@mail.gmail.com> (raw)
In-Reply-To: <20111208153738.GF11859@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2147 bytes --]
On Thu, Dec 8, 2011 at 10:37 AM, Michael Olbrich
<m.olbrich@pengutronix.de>wrote:
> Hi,
>
> so I accidentally pushed it before I could really review it...
> I had some time today and I think it's at least better than before.
>
> On Tue, Nov 29, 2011 at 03:59:41PM +0000, Benoît BURNICHON wrote:
> > Now, ptxd_ipkg_rev_smaller does not enforce a revision to be 1.2.3-4 but
> > allows everything debian like.
>
> Well, not everything debian like, '~' is not handled correctly, right?
> Maybe something like this:
> ------------------------------------------------------------------------
> --- libptxdist.sh 2011-12-08 16:11:21.143970557 +0100
> +++ libptxdist.sh 2011-12-08 16:15:00.300421956 +0100
> @@ -741,13 +741,14 @@
> #
> ptxd_ipkg_rev_decimal_convert() {
> local ver=$*
> - while echo $ver | grep -q '[^0-9.]'
> + while echo $ver | grep -q '[^0-9.~]'
> do
> - local char=`echo -n $ver | sed 's/.*\([^0-9.]\).*/\1/'`
> + local char=`echo -n $ver | sed 's/.*\([^0-9.~]\).*/\1/'`
> local char_dec=`echo -n $char | od -b | head -n 1 | awk
> '{print $2}'`
> ver=`echo $ver | sed "s/$char/.$char_dec/g"`
> done
>
> + ver=`echo $ver | sed -r "s/\.?~/.-1/g"`
> ver=`echo $ver | sed 's/\.\./.0/g'`
>
> echo "$ver"
> ------------------------------------------------------------------------
>
> So I've been thinking about this whole version issue. The next step would
> be all versions with '-'. Maybe we should always add '-1' as packages
> revision. That would solve the problem for most of the packages is the
> list, you posted some time ago.
> What remains are 'broken' versions. For those few we could do, e.g.:
>
> MYSQL_VERSION := 5.1.14-beta
> MYSQL_XPKG_VERSION := 5.1.14~beta
>
> Sounds like a good idea.
Seems like the pkg_XPKG_VERSION could be autogenerated based on the
pkg_VERSION so you wouldn't have to update all the package files. If there
is no '-' character in the version then pkg_XPKG_VERSION would be equal to
pkg_VERSION
Jon
[-- Attachment #1.2: Type: text/html, Size: 2745 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2011-12-08 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 15:59 Benoît BURNICHON
2011-12-02 15:26 ` Michael Olbrich
2011-12-03 4:46 ` [ptxdist] [PATCH] ptxd_ipkg_rev_smaller: fix compare Jon Ringle
2011-12-05 10:35 ` [ptxdist] [PATCH] ptxdist-2011.01.0 bug in make ipkg-push Benoît BURNICHON
2011-12-08 15:37 ` Michael Olbrich
2011-12-08 15:41 ` Michael Olbrich
2011-12-08 15:45 ` Jon Ringle [this message]
2011-12-08 15:55 ` Michael Olbrich
2011-12-08 17:38 ` Benoît BURNICHON
2011-12-09 10:09 ` Michael Olbrich
2011-12-09 14:20 ` [ptxdist] [PATCH] more pkg_xpkg_version sanitizing Michael Olbrich
2011-12-12 16:51 ` Jon Ringle
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=CAMwGMjzuoxO4LNaiei1-52LAa4kDj_1Lb_1Sf+YjJ1CDXCZHuA@mail.gmail.com \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox