From: Per Andersson <avtobiff@gmail.com>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: "supmua@googlegroups.com" <supmua@googlegroups.com>
Subject: Re: Generate man pages before dist (WAS Re: [sup] Release 0.20.0)
Date: Tue, 7 Oct 2014 12:47:02 +0200 [thread overview]
Message-ID: <CABYrXSQV=4BdMmBvjpnNvfvNicBcuRK8ztq_n1nDqjixj2ONvA@mail.gmail.com> (raw)
In-Reply-To: <1412676016-astroid-0-teg6538fjs-12315@strange>
On Tue, Oct 7, 2014 at 12:03 PM, Gaute Hope <eg@gaute.vetsj.com> wrote:
> Excerpts from Per Andersson's message of October 7, 2014 11:56:
>
(...)
>>>
>>> We've got man pages (Mr. Andersson)!
>>
>>
>> Is it possible to generate the man pages upon release and commit them
>> to, say, docs/man.
>>
>> That would make the Debian packaging much simpler, otherwise I have
>> to do that myself manually and put them in the debian directory. (It will
>> probably be easy to miss shipping updated man page in the Debian
>> package.)
>>
>> Debian packages should be buildable without network access, so using
>> the git submodule at build time will not work.
>
>
> The man files should be included in the man/ directory in the gem. You
> can check out the contents of the built gem by unpacking it manually:
>
> $ tar xf sup-0.20.0.gem
> $ tar xf data.tar.gz
>
> so all necessary files for a release should be included. I would suggest
> starting the source build off the .gem with the pre-generated man pages.
>
> Does that work for you?
Ah, clever. I like to use the actual upstream source myself though.
I'll just build and ship them in the Debian package.
--
Per
prev parent reply other threads:[~2014-10-07 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 9:56 Per Andersson
2014-10-07 10:03 ` Gaute Hope
2014-10-07 10:47 ` Per Andersson [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='CABYrXSQV=4BdMmBvjpnNvfvNicBcuRK8ztq_n1nDqjixj2ONvA@mail.gmail.com' \
--to=avtobiff@gmail.com \
--cc=eg@gaute.vetsj.com \
--cc=supmua@googlegroups.com \
/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