From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yann E. MORIN Date: Sun, 7 Aug 2011 21:24:17 +0200 Subject: [Buildroot] [RFC] Using AsciiDoc for the Buildroot manual In-Reply-To: <87wrepkp28.fsf@macbook.be.48ers.dk> References: <20110805102251.7a293244@skate> <87wrepkp28.fsf@macbook.be.48ers.dk> Message-ID: <201108072124.17460.yann.morin.1998@anciens.enib.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Peter, Thomas, All, On Sunday 07 August 2011 21:18:55 Peter Korsgaard wrote: > >> 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. I can take a look if you want. Thomas, is your 'asciidoc-manual' up-to-date? Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'