From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add gerbv.
Date: Wed, 02 Sep 2015 08:31:00 +0200 [thread overview]
Message-ID: <877fo949jv.fsf@elephly.net> (raw)
In-Reply-To: <87r3mhet9q.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
>> * gnu/packages/gettext.scm (po4a): New variable.
>
> [...]
>
>> + (string-append "--nonet "
>> + (assoc-ref inputs "docbook-xsl")
>> + ;; TODO: replace version string
>> + "/xml/xsl/docbook-xsl-" "1.78.1"
>> + "/manpages/docbook.xsl")))
>
> ... can this be avoided altogether by adding libxml2 as an input (which
> sets $XML_CATALOG_FILES as a side-effect)?
Oh, I did not know this. Yes, with libxml2 as an input this hackery is
not needed. Thanks!
>> * gnu/packages/engineering.scm (gerbv): New variable.
>
> [...]
>
>> + ;; Build rules contain references to Russian translation, but the
>> + ;; needed files are missing; see
>> + ;; http://sourceforge.net/p/gerbv/bugs/174/
>> + (delete-file "po/LINGUAS")
>> + (substitute* "man/Makefile.am"
>> + (("PO_FILES= gerbv.ru.1.in.po") "")
>> + (("man_MANS = gerbv.1 gerbv.ru.1") "man_MANS = gerbv.1"))
>> + (zero? (system* "autoreconf" "-vfi")))))))
>
> Could you modify Makefile.in instead? That would hopefully allow us to
> remove the dependency on the autotools.
Unfortunately, the tarball comes without the ‘configure’ script, so we
need to use autotools to generate it.
>> + "Gerbv is a Gerber file (RS-274X only) viewer. Gerbv lets you load
>
> What about giving a bit more context, along the lines of:
>
> Gerbv is a viewer for files in the Gerber format (RS-274X only), which
> is commonly used to represent printed circuit board (PCB) layouts.
Okay. I’ll push with these changes. Thanks for the review!
~~ Ricardo
prev parent reply other threads:[~2015-09-02 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 6:50 [PATCH] Add gerbv Ricardo Wurmus
2015-09-01 21:14 ` Ludovic Courtès
2015-09-02 6:31 ` Ricardo Wurmus [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=877fo949jv.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
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.