All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sven Oliver Moll <svolli@svolli.de>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/most: bump version to 5.2.0
Date: Tue, 30 Aug 2022 09:43:47 +0200	[thread overview]
Message-ID: <20220830094347.312e037c@windsurf> (raw)
In-Reply-To: <alpine.DEB.2.20.2208292318200.18923@defender.svolli.xa>

Hello Sven,

(Replying with the Buildroot list in Cc, stripping parts that could be
considered not relevant for the list)

On Mon, 29 Aug 2022 23:33:13 +0200 (CEST)
Sven Oliver Moll <svolli@svolli.de> wrote:

> This also leaves me with a question: I did run my check by just running 
> "make all". Now I've learned that "make legal-info" is something that I also 
> should check. Are there any other make targets I should test also next time?

The most relevant tool is utils/test-pkg. You feed it a small snippet
config file, like:

BR2_PACKAGE_MOST=y

and it will build test this package against a useful selection of
toolchain configurations. And as part of this, it will also run "make
legal-info" and bail out if it no longer works.

Hope this helps!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-08-30  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 15:14 [Buildroot] [PATCH 1/1] package/most: bump version to 5.2.0 Sven Oliver Moll
2022-08-29 20:18 ` Thomas Petazzoni via buildroot
     [not found]   ` <alpine.DEB.2.20.2208292318200.18923@defender.svolli.xa>
2022-08-30  7:43     ` Thomas Petazzoni via buildroot [this message]

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=20220830094347.312e037c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=svolli@svolli.de \
    --cc=thomas.petazzoni@bootlin.com \
    /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.