From: Matt Turner <mattst88@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Migrating man page to asciidoc?
Date: Sun, 26 Jun 2011 11:44:55 -0400 [thread overview]
Message-ID: <BANLkTi=a42uDxxEo2Re0JPsoctrDwx8MWQ@mail.gmail.com> (raw)
In-Reply-To: <4E06BC27.3020808@gentoo.org>
On Sun, Jun 26, 2011 at 12:57 AM, Sebastian Pipping <sping@gentoo.org> wrote:
>> * Now we need to have a build time dependency, at least for the live
>> ebuild, which pulls in about 34mb of downloads just to build the man
>> page.
>>
>> Since we are just talking about a man page, imho this is a lot of bloat
>> for very little gain.
>
> I disagree on bloat and on little gain.
>
> If you insist on changing status quo I would like to call in a vote.
Well, in fairness, the asciidoc dependency was just added a day or so ago.
But, I really don't think it's as big a problem as this long email
thread warrants. We simply want to avoid asciidoc, and specifically
it's dependencies, for catalyst snapshots. For the live ebuild, I
don't see the dependencies as a problem.
Can't we simply get the timestamp of the last commit to the git
branch/tag that we're making an archive from and apply it to the
generated content? Doing this would allow us to reproduce an identical
tarball, and avoids a lot of other problems discussed in this thread.
Thanks,
Matt
next prev parent reply other threads:[~2011-06-26 15:45 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 0:41 [gentoo-catalyst] Migrating man page to asciidoc? Sebastian Pipping
2011-06-24 7:07 ` Peter Volkov
2011-06-24 17:16 ` Sebastian Pipping
2011-06-25 17:30 ` Matt Turner
2011-06-25 17:50 ` Sebastian Pipping
2011-06-25 18:31 ` Matt Turner
2011-06-26 2:02 ` Matt Turner
2011-06-26 2:36 ` Sebastian Pipping
2011-06-26 2:49 ` William Hubbs
2011-06-26 3:14 ` Sebastian Pipping
2011-06-26 3:36 ` William Hubbs
2011-06-26 3:46 ` William Hubbs
2011-06-26 3:59 ` Sebastian Pipping
2011-06-26 3:49 ` Sebastian Pipping
2011-06-26 4:33 ` William Hubbs
2011-06-26 4:57 ` Sebastian Pipping
2011-06-26 15:44 ` Matt Turner [this message]
2011-06-26 17:33 ` William Hubbs
2011-06-26 17:55 ` Peter Stuge
2011-06-26 18:02 ` Matt Turner
2011-06-26 18:08 ` Peter Stuge
2011-06-26 23:01 ` Matt Turner
2011-06-26 23:26 ` Jorge Manuel B. S. Vicetto
2011-06-27 0:00 ` Peter Stuge
2011-06-27 0:31 ` Jorge Manuel B. S. Vicetto
2011-06-27 1:06 ` Peter Stuge
2011-06-27 1:43 ` Sebastian Pipping
2011-06-27 3:58 ` Jorge Manuel B. S. Vicetto
2011-06-27 15:55 ` Sebastian Pipping
2011-07-03 23:28 ` Sebastian Pipping
2011-07-04 0:10 ` Matt Turner
2011-07-04 0:18 ` Sebastian Pipping
2011-06-27 0:39 ` Peter Stuge
2011-06-26 17:55 ` Matt Turner
2011-06-26 18:17 ` Sebastian Pipping
2011-06-26 19:25 ` William Hubbs
2011-06-26 4:10 ` Matt Turner
2011-06-26 4:14 ` Sebastian Pipping
2011-06-26 4:44 ` William Hubbs
2011-06-26 4:46 ` Sebastian Pipping
2011-06-27 6:33 ` Peter Volkov
2011-06-26 16:48 ` Sebastian Pipping
2011-06-26 17:04 ` Peter Stuge
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='BANLkTi=a42uDxxEo2Re0JPsoctrDwx8MWQ@mail.gmail.com' \
--to=mattst88@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.org \
/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