From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 02/22] gettext: warn that legal-info is not implemented
Date: Wed, 09 May 2012 09:30:07 +0200 [thread overview]
Message-ID: <4FAA1CFF.5090300@lucaceresoli.net> (raw)
In-Reply-To: <CAAXf6LW4v94Z8U8wtfCkdRQZ85qEM4p2GQNvAsDgijSW_ZSvYw@mail.gmail.com>
Thomas De Schampheleire wrote:
> On Mon, May 7, 2012 at 10:12 PM, Luca Ceresoli<luca@lucaceresoli.net> wrote:
>> Signed-off-by: Luca Ceresoli<luca@lucaceresoli.net>
>> ---
>> package/gettext/gettext.mk | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/package/gettext/gettext.mk b/package/gettext/gettext.mk
>> index f3605da..1d9d84d 100644
>> --- a/package/gettext/gettext.mk
>> +++ b/package/gettext/gettext.mk
>> @@ -113,6 +113,9 @@ $(STAGING_DIR)/$(GETTEXT_TARGET_BINARY): $(GETTEXT_DIR)/$(GETTEXT_BINARY)
>> autopoint envsubst gettext.sh gettextize msg* ?gettext)
>> touch -c $@
>>
>> +gettext-legal-info:
>> + @$(call legal-warning-pkg,gettext,cannot produce any legal info)
>> +
> I don't think this statement is not entirely correct. It's not that we
> 'cannot' produce the info. It's just that currently, we did not add
> the necessary license definitions, right?
> What about something like 'legal-info not yet implemented' or 'no
> legal info saved yet' or ...?
Yes, 'legal-info not yet implemented' is more understandable.
I'll change that.
> Moreover, will this be added to each package for which no legal info
> is provided? What about making this message the default by putting it
> in pkg-gentargets.mk, if no suitable variables were defined?
Gentargets packages without _LICENSE / _LICENSE_FILES defined are handled
automatically by gentargets. They get listed in the manifest this way:
$ cat legal-info/manifest.csv
package,version,license,license files,source archive
...
freetype,2.4.8,unknown,not saved,freetype-2.4.8.tar.bz2
The problem with non-gentargets packages is that they do not get listed
automatically in the manifest, because the manifest is produced by the
gentargets infrastrucure.
Hence we should:
- convert these packages to gentargets, or
- manually implement a<PKG>-legal-info for these packages, or
- make the user aware that these packages are not handled by the legal-info
stuff: no manifest entry, no tarball, no license files.
The first option is the best thing to do, but it's out of the scope of this
patchset. The number of manual packages is consistently approaching zero
anyway.
I don't like the second option: this is work that would mostly be wasted when
converting to gentargets. I would rather spend my time converting to
gentargets.
The third option is the warning you see.
Luca
next prev parent reply other threads:[~2012-05-09 7:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 20:10 [Buildroot] [PATCH v3 00/22] Automatically produce legal compliance info Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 01/22] legal-info: infrastructure to collect legally-relevant material Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 02/22] gettext: warn that legal-info is not implemented Luca Ceresoli
2012-05-09 6:21 ` Thomas De Schampheleire
2012-05-09 6:34 ` Thomas Petazzoni
2012-05-09 7:30 ` Luca Ceresoli [this message]
2012-05-09 8:02 ` Thomas De Schampheleire
2012-05-07 20:12 ` [Buildroot] [PATCH v3 03/22] netkitbase: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 04/22] netkittelnet: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 05/22] newt: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 06/22] ttcp: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 07/22] vpnc: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 08/22] manual: document usage of the legal-info feature Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 09/22] manual: add advice about GPL compliance for Buildroot Luca Ceresoli
2012-05-09 6:05 ` Thomas De Schampheleire
2012-05-17 17:08 ` Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 10/22] linux: define license Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 11/22] m4: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 12/22] mpc: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 13/22] fakeroot: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 14/22] bzip2: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 15/22] directfb: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 16/22] iostat: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 17/22] lzo: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 18/22] lzop: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 19/22] libusb: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 20/22] pcre: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 21/22] netsnmp: " Luca Ceresoli
2012-05-07 20:12 ` [Buildroot] [PATCH v3 22/22] berkeleydb: " Luca Ceresoli
2012-05-12 23:10 ` [Buildroot] [PATCH v3 01/22] legal-info: infrastructure to collect legally-relevant material Arnout Vandecappelle
2012-05-14 16:54 ` Luca Ceresoli
2012-05-15 20:02 ` Arnout Vandecappelle
2012-05-14 19:16 ` Peter Korsgaard
2012-05-09 8:00 ` [Buildroot] [PATCH v3 00/22] Automatically produce legal compliance info Thomas De Schampheleire
2012-05-17 17:06 ` 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=4FAA1CFF.5090300@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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