From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] manual: add a make target 'manual-update-lists'
Date: Tue, 12 Mar 2013 23:04:04 +0100 [thread overview]
Message-ID: <513FA654.5020401@mind.be> (raw)
In-Reply-To: <20130312085945.7d595fb2@skate>
On 03/12/13 08:59, Thomas Petazzoni wrote:
> Dear Samuel Martin,
>
> On Tue, 12 Mar 2013 05:47:15 +0100, Samuel Martin wrote:
>
>> +manual-update-lists:
>> + @$(call MESSAGE,"Updating the manual lists...")
>> + $(Q)BR2_DEFCONFIG="" TOPDIR=$(TOPDIR) \
>> + $(TOPDIR)/support/scripts/gen-manual-lists.py
>
> Sorry if this has been discussed before. Why don't we make this part of
> the normal manual build process (make manual-pdf, make manual-html,
> etc.), so that we don't have to version control the generated lists of
> packages, and this updating of the lists is done automatically whenever
> we generate the manual?
Originally, the generated list was still modified manually. But I don't
think that is needed anymore, so indeed I would do it automatically as
part of the 'make manual' step.
Regards,
Arnout
--
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:[~2013-03-12 22:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 4:47 [Buildroot] [pull request v4] Pull request for branch for-master/doc Samuel Martin
2013-03-12 4:47 ` [Buildroot] [PATCH 1/5] support/scripts: add gen-manual-lists.py Samuel Martin
2013-03-12 4:47 ` [Buildroot] [PATCH 2/5] manual: add a make target 'manual-update-lists' Samuel Martin
2013-03-12 7:59 ` Thomas Petazzoni
2013-03-12 8:41 ` Samuel Martin
2013-03-13 7:39 ` Thomas Petazzoni
2013-03-19 21:52 ` Samuel Martin
2013-03-20 8:25 ` Thomas Petazzoni
2013-03-20 12:58 ` Lionel Orry
2013-03-20 13:49 ` Thomas Petazzoni
2013-03-12 22:04 ` Arnout Vandecappelle [this message]
2013-03-12 4:47 ` [Buildroot] [PATCH 3/5] manual: cleanup appendix.txt Samuel Martin
2013-03-12 4:47 ` [Buildroot] [PATCH 4/5] Makefile: add to the release target a warning about the manual updates Samuel Martin
2013-03-12 4:47 ` [Buildroot] [PATCH 5/5] manual: update generated lists Samuel Martin
2013-03-13 19:48 ` [Buildroot] [pull request v4] Pull request for branch for-master/doc Arnout Vandecappelle
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=513FA654.5020401@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 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.