All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Package informations, online and updated
Date: Thu, 2 Aug 2012 16:31:33 +0200	[thread overview]
Message-ID: <20120802163133.7c19d637@skate> (raw)
In-Reply-To: <CA+wH296kBL8ZhhrHW7KCdrvFRuhB3-B=H2yJwZTyu75A8FhJyA@mail.gmail.com>

Le Thu, 2 Aug 2012 15:19:15 +0100,
Alex Bradbury <asb@asbradbury.org> a ?crit :

> It would be handy to add the current version for each package. More
> ambitiously, a variable defining a watch[1] line could be added to
> each Makefile, and used with the Debian scripts (such as uscan) to
> automatically detect new upstream versions.

Agreed. Funnily I was almost to the point of talking about this in my
announcement e-mail :-)

How exactly are those watch lines used? I.e, which tool is capable of
parsing them, and doing the necessary http/ftp requests to figure out
if a newer upstream version is available?

That said, showing the version of each package will slow down the
script quite a bit. For now, the script simply greps/seds through
the .mk file, which is reasonably fast. However, knowing the version
number is more complicated because sometimes the version number is
computed from other variables:

FOO_MAJOR_VERSION = 2
FOO_VERSION = $(FOO_MAJOR_VERSION).3

So to handle this properly, I would have to do 'make
<pkg>-show-version' for each package, which would be very slow
(but doable).

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-08-02 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 19:37 [Buildroot] Package informations, online and updated Thomas Petazzoni
2012-08-01 18:55 ` Thomas De Schampheleire
2012-08-01 18:58   ` Thomas Petazzoni
2012-08-02 14:19 ` Alex Bradbury
2012-08-02 14:31   ` Thomas Petazzoni [this message]
2012-08-02 14:53     ` Alex Bradbury
2012-08-02 14:56       ` Thomas Petazzoni
2012-08-04 12:04 ` Samuel Martin
2012-08-04 12:30   ` Thomas Petazzoni
2012-08-04 12:53     ` Samuel Martin
2012-08-04 15:36       ` Thomas Petazzoni

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=20120802163133.7c19d637@skate \
    --to=thomas.petazzoni@free-electrons.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.