public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Migrating man page to asciidoc?
Date: Sat, 25 Jun 2011 21:49:29 -0500	[thread overview]
Message-ID: <20110626024929.GA6506@linux1> (raw)
In-Reply-To: <4E069B1F.8040409@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2900 bytes --]

On Sun, Jun 26, 2011 at 04:36:15AM +0200, Sebastian Pipping wrote:
> On 06/26/2011 04:02 AM, Matt Turner wrote:
> > I get this when trying to do `EGIT_BRANCH="catalyst_2" emerge
> > =catalyst-9999` I suppose because asciidoc isn't listed as a
> > dependency.
> > 
> > ./doc/make_subarch_table_guidexml.py
> > a2x --conf-file=doc/asciidoc.conf --attribute="catalystversion=`fgrep
> > '__version__=' catalyst | sed 's|^__version__="\(.*\)"$|\1|'`" \
> >          --format=manpage -D files "doc/catalyst.1.txt"
> > /bin/sh: a2x: command not found
> > make: *** [files/catalyst.1] Error 127
> > emake failed
> 
> Correct, asciidoc is missing.
> 
> 
> > but I see that asciidoc has quite a number of dependencies.
> > 
> > [ebuild  N     ] media-libs/jpeg-8c  USE="-static-libs"
> > [ebuild  N     ] app-text/build-docbook-catalog-1.6
> > [ebuild  N     ] media-libs/libpng-1.4.7  USE="-apng -static-libs"
> > [ebuild  N     ] virtual/jpeg-0  USE="-static-libs"
> > [ebuild  N     ] dev-libs/libgpg-error-1.10  USE="nls -common-lisp
> > -static-libs"
> > [ebuild  N     ] app-text/sgml-common-0.6.3-r5
> > [ebuild  N     ] dev-lang/swig-2.0.4  USE="pcre -ccache -doc"
> > [ebuild  N     ] dev-util/gtk-doc-am-1.17
> > [ebuild  N     ] app-text/docbook-xsl-stylesheets-1.76.1
> > [ebuild  N     ] dev-libs/libgcrypt-1.5.0_beta1-r2  USE="-static-libs"
> > [ebuild  N     ] media-libs/gd-2.0.35-r3  USE="fontconfig jpeg png
> > truetype zlib -static-libs -xpm"
> > [ebuild  N     ] dev-libs/glib-2.28.8  USE="static-libs -debug -doc
> > -fam (-introspection) (-selinux) -test -xattr"
> > [ebuild  N     ] media-gfx/graphviz-2.26.3-r3  USE="nls perl python
> > -cairo -doc -examples -gtk (-java) -lasi -ruby -static-libs -tcl"
> > [ebuild  N     ] app-text/docbook-xml-dtd-4.5-r1
> > [ebuild  N     ] dev-libs/libxslt-1.1.26-r1  USE="crypt python -debug"
> > [ebuild  N     ] app-text/asciidoc-8.6.5  USE="-examples -highlight
> > -test -vim-syntax"
> > 
> > Is there some way we can slim this down? Presumably asciidoc isn't
> > going to be using any image-related programs for generating a man
> > page.
> 
> The image stuff is indirect dependencies, see --tree.
> 
> Future releases of catalyst do not have this problem as the make file
> comes pre-rendered with the tarball.  This is a live-ebuild issue.

No, we can't have the manpage pre-rendered in the tarball, because that
makes the tarball different every time it is created since the
date/timestamps in the archive will be different. In other words, it is
not possible for anyone to ever reproduce the exact same tarball that we
produce.

I see two ways around this: We can either make asciidoc a build time
dependency so that the user can use something like "make manpage" to
generate the manpage or we can go back to the manpage that is in the git
repository.

Thoughts?

William


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-06-26  2:49 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 [this message]
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
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=20110626024929.GA6506@linux1 \
    --to=williamh@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