Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/6] manual: add package-list.txt generation support
Date: Thu, 29 Nov 2012 21:48:31 +0100	[thread overview]
Message-ID: <50B7CA1F.2010504@mind.be> (raw)
In-Reply-To: <1354175268-6909-1-git-send-email-s.martin49@gmail.com>

On 29/11/12 08:47, Samuel Martin wrote:
>
> Signed-off-by: Samuel Martin<s.martin49@gmail.com>

Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
  (untested)

  But since I'm pedantic, I still have some comments :-)

[snip]
> diff --git a/support/scripts/gen-manual-pkg-list.sh b/support/scripts/gen-manual-pkg-list.sh
> new file mode 100755
> index 0000000..f11b4de
> --- /dev/null
> +++ b/support/scripts/gen-manual-pkg-list.sh
> @@ -0,0 +1,19 @@
> +#!/bin/sh
> +##
> +## gen-manual-pkg-list.sh
> +##
> +## Author(s):
> +##  - Samuel MARTIN<s.martin49@gmail.com>
> +##
> +## Copyright (C) 2012 Samuel MARTIN

  If you add a copyright statement, ideally you should also refer to the GPL:

     This program is free software; you can redistribute it and/or modify
     it under the terms of the GNU General Public License as published by
     the Free Software Foundation; either version 2 of the License, or
     (at your option) any later version.

(The fact that you put the Copyright statement there makes it look as if
it's proprietary.  Adding the GPL reference disambiguates it.  Of course,
it is implied by the global buildroot license even if you leave out the
GPL reference.)

> +##
> +
> +# Generate the manual package-list.txt content (in asciidoc format) and print it
> +# to the standard output.
> +
> +printf "\n//\n// Autogenerated file\n//\n\n"
> +printf "[[package-list]]\n"
> +printf "Available packages\n"
> +printf -- "------------------\n\n"

  Since this is now part of a script, you can just cat a here document.
Much more readable.

> +grep -rlE --color=never '\((autotools|cmake|generic)-package\)' package | \

  We globally unexport GREP_OPTIONS, so the --color=never is redundant.
In addition, it would barf on non-gnu-grep.


  Regards,
  Arnout

> +  sed -ne '/.*\/\(.*\).mk$/ s//* \1/p' | sort

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
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

      parent reply	other threads:[~2012-11-29 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29  7:47 [Buildroot] [PATCH v2 2/6] manual: add package-list.txt generation support Samuel Martin
2012-11-29  7:47 ` [Buildroot] [PATCH v2 3/6] manual: add deprecated-list.txt " Samuel Martin
2012-11-29 22:41   ` Arnout Vandecappelle
2012-11-29  7:47 ` [Buildroot] [PATCH v2 6/6] manual: add generated *-list.txt Samuel Martin
2012-11-29 22:42   ` Arnout Vandecappelle
2012-11-29 20:48 ` Arnout Vandecappelle [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=50B7CA1F.2010504@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