From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [External] Re: [PATCH v5] support/scripts/pkg-stats: add latest upstream version information
Date: Thu, 3 Jan 2019 22:16:04 +0100 [thread overview]
Message-ID: <20190103221604.4da001d1@windsurf> (raw)
In-Reply-To: <CA+fik51_toDs8PPL6wk8OZDNVTAkBb5a5CkuaPzk6JjnPDvzyQ@mail.gmail.com>
Hello,
On Thu, 3 Jan 2019 15:02:24 -0600, Brandon Maier wrote:
> Agreed it's not a pretty hack. I wouldn't want to handle the other
> oddities in here, as that would get messy. I suggested it for "v" only
> because it seems to be very common. It would be a way to get us most
> of the way there, then it could be reverted if e.g. all the github
> versions are fixed up.
>
> On those other packages though, perhaps adding an optional variable to
> package mk files for custom versions? E.g. package/libnfs/libnfs.mk
> defines version as "libnfs-3.0.0", but the r-m version is "3.0.0".
> E.g.
>
> package/libnfs/libnfs.mk:
> LIBNFS_RM_VERSION = 3.0.0
> LIBNFS_VERSION = libnfs-$(LIBNFS_RM_VERSION)
We could do that, but is that really needed/useful ?
> > It seems like I never posted them. I thought there was some discussion
> > on the list about this issue, but I can't find it. Perhaps I should
> > update this series, submit it for good, and see what the feedback is ?
>
> Regardless of this patch series, this sounds like a good idea to me.
> Especially considering Anitya does this too, as Yann mentioned[1].
>
> [1] https://github.com/release-monitoring/anitya/issues/374
Right. So you say I should submit this "fix-versions" patch series ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-03 21:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 8:38 [Buildroot] [PATCH v5] support/scripts/pkg-stats: add latest upstream version information Thomas Petazzoni
2019-01-03 8:40 ` Thomas Petazzoni
2019-01-03 19:57 ` Brandon Maier
2019-01-03 20:33 ` Thomas Petazzoni
2019-01-03 21:02 ` [Buildroot] [External] " Brandon Maier
2019-01-03 21:16 ` Thomas Petazzoni [this message]
2019-01-03 23:29 ` Brandon Maier
2019-01-03 20:38 ` [Buildroot] " Yann E. MORIN
[not found] ` <CANQCQpZHYrkUVrYUxqANd9xzicMz-9apDWYeUWYmHLqG6YA8wg@mail.gmail.com>
2019-01-03 20:23 ` [Buildroot] [External] " Matthew Weber
2019-01-04 2:12 ` [Buildroot] " Ricardo Martincoski
2019-01-04 14:54 ` Brandon Maier
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=20190103221604.4da001d1@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.