All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5 of 5] legal info: cleanup utility functions
Date: Sat, 05 Oct 2013 23:19:31 +0200	[thread overview]
Message-ID: <52508263.6020405@lucaceresoli.net> (raw)
In-Reply-To: <9939e8c5aeece3d9c897.1380892354@argentina>

Hi Thomas,

Thomas De Schampheleire wrote:
> The legal-info utility functions where defined using two ways
> util-foo = command-foo
> and
> define util-bar # parameter description
> 	command-bar
> endef
>
> This commit changes these functions to use the second form for clarity and
> additionally adds parameter descriptions on all functions.

Yeah, never liked what I wrote here...

But, in order to make the code een more readable, I suggest you to add
an empty line between definitions, just like the "define KCONFIG_*" above
in the same file.

Apart from this, and from a little note below,
Acked-by: Luca Ceresoli <luca@lucaceresoli.net>

>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
>
> ---
>   package/pkg-utils.mk |  16 +++++++++++-----
>   1 files changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/package/pkg-utils.mk b/package/pkg-utils.mk
> --- a/package/pkg-utils.mk
> +++ b/package/pkg-utils.mk
> @@ -91,17 +91,23 @@ endef
>   # legal-info helper functions
>   #
>   LEGAL_INFO_SEPARATOR="::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::"
> -legal-warning=echo "WARNING: $(1)" >>$(LEGAL_WARNINGS)
> -legal-warning-pkg=echo "WARNING: $(1): $(2)" >>$(LEGAL_WARNINGS)
> +define legal-warning # text
> +	echo "WARNING: $(1)" >>$(LEGAL_WARNINGS)
> +endef
> +define legal-warning-pkg # pkg, text
> +	echo "WARNING: $(1): $(2)" >>$(LEGAL_WARNINGS)
> +endef
>   define legal-warning-pkg-savednothing # pkg, {local|override}
>   	$(call legal-warning-pkg,$(1),sources and license files not saved ($(2) packages not handled))
>   endef
> -legal-manifest=echo '"$(1)","$(2)","$(3)","$(4)","$(5)"' >>$(LEGAL_MANIFEST_CSV_$(6))
> -define legal-license-header
> +define legal-manifest # pkg, version, license, license-files, source, type

"type" is too generic to convey a meaning here. How about "{host|target}"?

-- 
Luca

      reply	other threads:[~2013-10-05 21:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 13:12 [Buildroot] [PATCH 0 of 5] legal info: split host and package output Thomas De Schampheleire
2013-10-04 13:12 ` [Buildroot] [PATCH 1 of 5] legal info: fix saving of host package licenses Thomas De Schampheleire
2013-10-04 13:24   ` Thomas De Schampheleire
2013-10-04 15:29     ` Thomas De Schampheleire
2013-10-07 15:01       ` Thomas De Schampheleire
2013-10-04 13:12 ` [Buildroot] [PATCH 2 of 5] legal info: split manifest for host and target Thomas De Schampheleire
2013-10-04 13:12 ` [Buildroot] [PATCH 3 of 5] legal-info: split license texts " Thomas De Schampheleire
2013-10-04 14:08   ` Thomas De Schampheleire
2013-10-05 21:28   ` Luca Ceresoli
2013-10-04 13:12 ` [Buildroot] [PATCH 4 of 5] legal info: split sources " Thomas De Schampheleire
2013-10-05 21:29   ` Luca Ceresoli
2013-10-04 13:12 ` [Buildroot] [PATCH 5 of 5] legal info: cleanup utility functions Thomas De Schampheleire
2013-10-05 21:19   ` Luca Ceresoli [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=52508263.6020405@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 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.