From: Mark H Weaver <mhw@netris.org>
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: docbook-xsl version number in pathname (was Re: [PATCH] gnu: Add moreutils.)
Date: Sun, 01 Feb 2015 17:08:27 -0500 [thread overview]
Message-ID: <87oapde144.fsf_-_@netris.org> (raw)
In-Reply-To: <87vbjle1gi.fsf@netris.org> (Mark H. Weaver's message of "Sun, 01 Feb 2015 17:01:01 -0500")
Mark H Weaver <mhw@netris.org> writes:
> With these simplifications, it would look like this:
>
> (lambda* (#:key inputs #:allow-other-keys)
> (substitute* "Makefile"
> (("/usr/share/xml/.*/docbook.xsl")
> (string-append
> (assoc-ref inputs "docbook-xsl")
> "/xml/xsl/docbook-xsl-1.78.1/manpages/docbook.xsl"))))
I just realized, it's not good that the docbook-xsl version number is
hardcoded here. This will break the next time docbook-xsl is updated.
Does anyone know how to improve this?
The relevant bit in the package Makefile that is being modified is this:
DOCBOOK2XMAN=xsltproc --param man.authors.section.enabled 0 /usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl
Can we modify this command to avoid giving the full pathname? Or should
we modify our docbook-xsl package to add a symlink that allows us to
omit the version number?
Mark
next prev parent reply other threads:[~2015-02-01 22:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 1:23 [PATCH] gnu: Add moreutils Taylan Ulrich Bayırlı/Kammer
2015-02-01 1:44 ` David Thompson
2015-02-01 5:48 ` Mark H Weaver
2015-02-01 13:08 ` Taylan Ulrich Bayırlı/Kammer
2015-02-01 13:11 ` Taylan Ulrich Bayırlı/Kammer
2015-02-01 14:14 ` David Thompson
2015-02-01 14:51 ` Taylan Ulrich Bayırlı/Kammer
2015-02-01 22:01 ` Mark H Weaver
2015-02-01 22:08 ` Mark H Weaver [this message]
2015-02-02 0:16 ` docbook-xsl version number in pathname (was Re: [PATCH] gnu: Add moreutils.) Taylan Ulrich Bayırlı/Kammer
2015-02-13 15:10 ` Mark H Weaver
2015-02-02 21:51 ` [PATCH] gnu: Add moreutils Ludovic Courtès
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=87oapde144.fsf_-_@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.