From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Tool to check packages updates
Date: Wed, 23 Oct 2013 11:42:28 +0200 [thread overview]
Message-ID: <20131023114228.619fedd9@skate> (raw)
In-Reply-To: <CACjG4BJq5TXvpMAoU7w3JgTVrOGHpeKng88HU03Rf_=XunPKAQ@mail.gmail.com>
Arnaud,
On Tue, 22 Oct 2013 19:06:41 +0200, arnaud aujon wrote:
> As we talk earlier in the mailing list, I started working on a python
> script to automatically check if a package can be updated.
>
> For now, the result of the script is : 837 packages (115 up to date, 154
> old and 568 unknown)
> So the script is able to check that 115 packages are up to dates and that
> 154 have newer version or that the script is wrong.
> There is still a lot of work to have something usefull, I will post the
> script as soon as it's ready to be reviewed.
Thanks, definitely looks interesting. Please post your script when you
think it's ok, but don't wait to much: the earlier the better, so that
you can get early feedback, and maybe help/testing from others.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-23 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 17:06 [Buildroot] Tool to check packages updates arnaud aujon
2013-10-23 9:42 ` Thomas Petazzoni [this message]
2013-10-23 11:21 ` Thomas De Schampheleire
2013-10-23 15:43 ` arnaud aujon
2013-10-23 17:39 ` Arnout Vandecappelle
2013-10-23 18:58 ` arnaud aujon
2013-10-23 19:23 ` Thomas De Schampheleire
2013-10-23 20:30 ` arnaud aujon
2013-11-08 14:29 ` arnaud aujon
2013-11-08 14:35 ` Thomas Petazzoni
2013-11-20 15:34 ` arnaud aujon
2013-11-20 15:51 ` Thomas De Schampheleire
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=20131023114228.619fedd9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox