From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Sun, 07 Aug 2011 21:18:55 +0200 Subject: [Buildroot] [RFC] Using AsciiDoc for the Buildroot manual In-Reply-To: <20110805102251.7a293244@skate> (Thomas Petazzoni's message of "Fri, 5 Aug 2011 10:22:51 +0200") References: <20110805083926.257f81bc@skate> <87ipqcmhf7.fsf@macbook.be.48ers.dk> <20110805102251.7a293244@skate> Message-ID: <87wrepkp28.fsf@macbook.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Thomas" == Thomas Petazzoni writes: Hi, >> Indeed. For releases I think atleast the text and single-html >> version should get included in the tarball. Thomas> So, should we extend the release to target to uncompress the Thomas> tarball after it has been generated by git archive, generate Thomas> the documentation, add it to the release directory, and Thomas> re-create the tarball? Or is there a better way? I haven't looked in detail, but we can probably just use tar --append to add the documentation afterwards. >> We also need to setup something with >> a git hook to regenerate (some of) the documentation on the server >> whenever any of the source files changes. Currently the website is >> simply a git checkout managed from cron on the server, and there's no >> asciidoc on the server, but presumably that's just a question about >> asking the osuosl.org guys for it. Thomas> In order to move forward on this, can we start discussing this Thomas> with the osuosl.org people? Yes, I've already mailed them to get asciidoc installed and get control over the website update cronjob. -- Bye, Peter Korsgaard