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:56:42 +0200 [thread overview]
Message-ID: <20120802165642.677b9915@skate> (raw)
In-Reply-To: <CA+wH294hkqsmAA-KdCPuefNYkNvM6VkZj5cmxkNUjdnEZq6FxQ@mail.gmail.com>
Le Thu, 2 Aug 2012 15:53:44 +0100,
Alex Bradbury <asb@asbradbury.org> a ?crit :
> uscan: http://manpages.debian.net/cgi-bin/man.cgi?query=uscan
> http://anonscm.debian.org/gitweb/?p=devscripts/devscripts.git;a=blob;f=scripts/uscan.pl
>
> uscan wants to find a separate 'watch' file inside a debian/ dir. It
> actually looks like it might not be that hard to hack up uscan.pl so
> it just takes the watch line as an argument (though it's been a number
> of years since I hacked any Perl), then each package could have a
> check-upstream-version target which uses the watch line defined in
> that packages makefile and invokes the buildroot 'fork' of uscan.pl to
> check whether a newer release is available upstream. I don't know if
> any other distros have a similar sort of system, it just strikes me
> there's not much point reinventing the wheel here and it's handy to be
> able to just lift the watch regex from the debian/watch file for many
> packages.
Looks nice. Patches? :-)
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-08-02 14:56 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
2012-08-02 14:53 ` Alex Bradbury
2012-08-02 14:56 ` Thomas Petazzoni [this message]
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=20120802165642.677b9915@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.