| 1 |
On Sun, Jun 26, 2011 at 04:36:15AM +0200, Sebastian Pipping wrote: |
| 2 |
> On 06/26/2011 04:02 AM, Matt Turner wrote: |
| 3 |
> > I get this when trying to do `EGIT_BRANCH="catalyst_2" emerge |
| 4 |
> > =catalyst-9999` I suppose because asciidoc isn't listed as a |
| 5 |
> > dependency. |
| 6 |
> > |
| 7 |
> > ./doc/make_subarch_table_guidexml.py |
| 8 |
> > a2x --conf-file=doc/asciidoc.conf --attribute="catalystversion=`fgrep |
| 9 |
> > '__version__=' catalyst | sed 's|^__version__="\(.*\)"$|\1|'`" \ |
| 10 |
> > --format=manpage -D files "doc/catalyst.1.txt" |
| 11 |
> > /bin/sh: a2x: command not found |
| 12 |
> > make: *** [files/catalyst.1] Error 127 |
| 13 |
> > emake failed |
| 14 |
> |
| 15 |
> Correct, asciidoc is missing. |
| 16 |
> |
| 17 |
> |
| 18 |
> > but I see that asciidoc has quite a number of dependencies. |
| 19 |
> > |
| 20 |
> > [ebuild N ] media-libs/jpeg-8c USE="-static-libs" |
| 21 |
> > [ebuild N ] app-text/build-docbook-catalog-1.6 |
| 22 |
> > [ebuild N ] media-libs/libpng-1.4.7 USE="-apng -static-libs" |
| 23 |
> > [ebuild N ] virtual/jpeg-0 USE="-static-libs" |
| 24 |
> > [ebuild N ] dev-libs/libgpg-error-1.10 USE="nls -common-lisp |
| 25 |
> > -static-libs" |
| 26 |
> > [ebuild N ] app-text/sgml-common-0.6.3-r5 |
| 27 |
> > [ebuild N ] dev-lang/swig-2.0.4 USE="pcre -ccache -doc" |
| 28 |
> > [ebuild N ] dev-util/gtk-doc-am-1.17 |
| 29 |
> > [ebuild N ] app-text/docbook-xsl-stylesheets-1.76.1 |
| 30 |
> > [ebuild N ] dev-libs/libgcrypt-1.5.0_beta1-r2 USE="-static-libs" |
| 31 |
> > [ebuild N ] media-libs/gd-2.0.35-r3 USE="fontconfig jpeg png |
| 32 |
> > truetype zlib -static-libs -xpm" |
| 33 |
> > [ebuild N ] dev-libs/glib-2.28.8 USE="static-libs -debug -doc |
| 34 |
> > -fam (-introspection) (-selinux) -test -xattr" |
| 35 |
> > [ebuild N ] media-gfx/graphviz-2.26.3-r3 USE="nls perl python |
| 36 |
> > -cairo -doc -examples -gtk (-java) -lasi -ruby -static-libs -tcl" |
| 37 |
> > [ebuild N ] app-text/docbook-xml-dtd-4.5-r1 |
| 38 |
> > [ebuild N ] dev-libs/libxslt-1.1.26-r1 USE="crypt python -debug" |
| 39 |
> > [ebuild N ] app-text/asciidoc-8.6.5 USE="-examples -highlight |
| 40 |
> > -test -vim-syntax" |
| 41 |
> > |
| 42 |
> > Is there some way we can slim this down? Presumably asciidoc isn't |
| 43 |
> > going to be using any image-related programs for generating a man |
| 44 |
> > page. |
| 45 |
> |
| 46 |
> The image stuff is indirect dependencies, see --tree. |
| 47 |
> |
| 48 |
> Future releases of catalyst do not have this problem as the make file |
| 49 |
> comes pre-rendered with the tarball. This is a live-ebuild issue. |
| 50 |
|
| 51 |
No, we can't have the manpage pre-rendered in the tarball, because that |
| 52 |
makes the tarball different every time it is created since the |
| 53 |
date/timestamps in the archive will be different. In other words, it is |
| 54 |
not possible for anyone to ever reproduce the exact same tarball that we |
| 55 |
produce. |
| 56 |
|
| 57 |
I see two ways around this: We can either make asciidoc a build time |
| 58 |
dependency so that the user can use something like "make manpage" to |
| 59 |
generate the manpage or we can go back to the manpage that is in the git |
| 60 |
repository. |
| 61 |
|
| 62 |
Thoughts? |
| 63 |
|
| 64 |
William |
Archives