All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] package: remove 'v' prefix from github-fetched packages
Date: Thu, 20 Jun 2019 21:46:15 +0200	[thread overview]
Message-ID: <20190620214615.5c60748c@windsurf> (raw)
In-Reply-To: <348e13f5-efeb-7136-3315-ce437b12dad6@mind.be>

On Thu, 20 Jun 2019 21:33:44 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

> On 20/06/2019 08:31, Thomas Petazzoni wrote:
> > On Wed, 19 Jun 2019 22:50:01 +0200
> > Arnout Vandecappelle <arnout@mind.be> wrote:  
> [snip]
> >>  It would also be nice if we had some formal way of checking that new packages
> >> do this correctly. Actually, it would be good if pkg-stats could generate a
> >> report in a human-readable format so it could be used as part of the review flow
> >> to check if the mapping with release-monitoring is OK (plus all the other things
> >> pkg-stats evaluates).  
> > 
> > Hm, yes, could be an interesting idea. Just a new pkg-stats option ?  
> 
>  Actually, since pkg-stats is in support/scripts it's currently not supposed to
> be user-visible. So I'd rather turn it around: make the text output to stdout
> the default, and add an option to generate HTML.

While I agree, I don't understand the relationship with pkg-stats being
in support/scripts. Are you saying that we should then add a "make
<pkg>-check-upstream-version" target that would call pkg-stats with the
right options ?

I'm a bit confused here.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-06-20 19:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12  6:42 [Buildroot] [PATCH 0/4] Sanetize packages version Victor Huesca
2019-06-12  6:42 ` [Buildroot] [PATCH 1/4] package: remove 'v' prefix from github-fetched packages Victor Huesca
2019-06-19 20:50   ` Arnout Vandecappelle
2019-06-20  6:31     ` Thomas Petazzoni
2019-06-20 19:33       ` Arnout Vandecappelle
2019-06-20 19:46         ` Thomas Petazzoni [this message]
2019-06-20 21:07           ` Arnout Vandecappelle
2019-06-20 11:51     ` Victor Huesca
2019-06-20 19:31       ` Arnout Vandecappelle
2019-06-12  6:42 ` [Buildroot] [PATCH 2/4] package: remove 'v' prefix from tarball-fetched packages Victor Huesca
2019-06-19 21:06   ` Arnout Vandecappelle
2019-06-20  6:13     ` Thomas Petazzoni
2019-06-20  9:23       ` Victor Huesca
2019-06-20 19:43         ` Arnout Vandecappelle
2019-06-12  6:42 ` [Buildroot] [PATCH 3/4] package: remove non-conventional prefix/suffix from github-fetched packages Victor Huesca
2019-06-19 21:30   ` Arnout Vandecappelle
2019-06-20 12:42     ` Victor Huesca
2019-06-20 19:50       ` Arnout Vandecappelle
2019-06-21  2:15   ` Carlos Santos
2019-06-12  6:42 ` [Buildroot] [PATCH 4/4] package: remove non-conventional prefix/suffix from tarball-fetched packages Victor Huesca
2019-06-20 21:27   ` Arnout Vandecappelle
2019-06-12  7:26 ` [Buildroot] [PATCH 0/4] Sanetize packages version Thomas Petazzoni
2019-06-12  8:39   ` Victor Huesca
2019-06-12 14:50     ` Thomas Petazzoni
2019-06-19 15:35       ` Victor Huesca
2019-06-20 20:32         ` Arnout Vandecappelle
2019-06-23 16:33           ` Thomas Petazzoni
2019-06-12  8:51   ` Arnout Vandecappelle
2019-06-18 12:11     ` Victor Huesca

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=20190620214615.5c60748c@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.