From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 1/4] legal-info: remove FOO_MANIFEST_TARBALL and FOO_MANIFEST_SITE defaults
Date: Mon, 02 Feb 2015 22:28:25 +0100 [thread overview]
Message-ID: <54CFEBF9.1010400@mind.be> (raw)
In-Reply-To: <1420199015-16907-2-git-send-email-luca@lucaceresoli.net>
On 02/01/15 12:43, Luca Ceresoli wrote:
> When FOO_SOURCE is non-empty, FOO_MANIFEST_TARBALL is always set.
> When FOO_SOURCE is empty, FOO_MANIFEST_TARBALL is not set, but also
> never used, due to the if below which defuses the whole legal-info
> processing for packages that have FOO_SOURCE explicitly set to an
> empty string.
>
> So get rid of the default assignment to "not saved".
>
> Do it for FOO_MANIFEST_SITE as well: it is pointless to have
> FOO_MANIFEST_SITE with an empty FOO_SOURCE in a package. A quick
> grep session in the sources confirmed this assumption is indeed
> true for the current code.
>
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
> Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> package/pkg-generic.mk | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/package/pkg-generic.mk b/package/pkg-generic.mk
> index 9643a30..38ef581 100644
> --- a/package/pkg-generic.mk
> +++ b/package/pkg-generic.mk
> @@ -653,8 +653,6 @@ $(2)_MANIFEST_SITE = $$(call qstrip,$$($(2)_SITE))
> endif
> endif
> endif
> -$(2)_MANIFEST_TARBALL ?= not saved
> -$(2)_MANIFEST_SITE ?= not saved
>
> # legal-info: produce legally relevant info.
> $(1)-legal-info:
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-02-02 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 11:43 [Buildroot] [RFC 0/4] legal-info: save the external-toolchain source archive Luca Ceresoli
2015-01-02 11:43 ` [Buildroot] [RFC 1/4] legal-info: remove FOO_MANIFEST_TARBALL and FOO_MANIFEST_SITE defaults Luca Ceresoli
2015-02-02 21:28 ` Arnout Vandecappelle [this message]
2015-02-02 21:49 ` Peter Korsgaard
2015-01-02 11:43 ` [Buildroot] [RFC 2/4] legal-info: allow to declare the actual sources for binary packages Luca Ceresoli
2015-02-02 21:47 ` Arnout Vandecappelle
2015-02-02 21:49 ` Arnout Vandecappelle
2015-02-05 13:44 ` Luca Ceresoli
2015-04-21 14:54 ` Luca Ceresoli
2015-01-02 11:43 ` [Buildroot] [RFC 3/4] toolchain-externel: mass-define actual source tarball for known patterns Luca Ceresoli
2015-02-02 21:57 ` Arnout Vandecappelle
2015-01-02 11:43 ` [Buildroot] [RFC 4/4] toolchain-external: define actual sources for arago toolchains Luca Ceresoli
2015-02-02 21:58 ` Arnout Vandecappelle
2015-02-02 21:24 ` [Buildroot] [RFC 0/4] legal-info: save the external-toolchain source archive Arnout Vandecappelle
2015-02-05 13:25 ` Luca Ceresoli
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=54CFEBF9.1010400@mind.be \
--to=arnout@mind.be \
--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