all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <bavier@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add Asymptote.
Date: Fri, 01 Jan 2016 19:10:07 +0100	[thread overview]
Message-ID: <87si2hgohs.fsf@gnu.org> (raw)
In-Reply-To: <20151231143047.1f62f832@member.fsf.org> (Eric Bavier's message of "Thu, 31 Dec 2015 14:30:47 -0600")

Eric Bavier <bavier@member.fsf.org> skribis:

> On Wed, 30 Dec 2015 17:11:08 +0100
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> Eric Bavier <bavier@member.fsf.org> skribis:
>> 
>> > * gnu/packages/plotutils.scm (asymptote): New variable.
>> > * gnu/packages/patches/asymptote-gsl2.patch: New file.
>> > * gnu-system.am (dist_patch_DATA): Add it.  
>> 
>> [...]
>> 
>> > +    (native-inputs
>> > +     `(("gs" ,ghostscript)              ;For tests
>> > +       ("texinfo" ,texinfo)             ;For generating documentation
>> > +       ("texlive" ,texlive)             ;For tests and documentation  
>> 
>> Would it be enough to depend on texlive-bin?
>
> Both tests and documentation creation depend on various .fmt and .sty
> files from the texlive package, so texlive-bin would not be enough it
> seems.

OK.

>> Alternately, could documentation be made a separate package?
>
> Do you mean "package" rather than "output"?

I was thinking of a separate package (as done for NumPy IIRC), but maybe
that’s impractical.

> I had tried doing a separate output originally. The issue is that the
> 'asy' binary in "out" ends up with a reference to the "doc" output for
> the 'help' command in its interactive mode.

OK.  Perhaps you could leave that as a comment to future readers who
will want to do the same.  :-)

The same problem arises with TeX Live itself, where ‘texdoc’ keeps a
reference to the documentation directory, preventing the addition of a
separate output.  Similarly with Perl and ‘perldoc’.  Annoying!

>> Otherwise LGTM, thanks!
>
> Attached is an updated patch suitable for master that adds a
> libgc-for-c++ since it's a semi-private package.  Is this alright, or
> should it be two patches?

That’s OK.

> From 2faf8a6c093739c4b8980b337a6a0ed659e84ebf Mon Sep 17 00:00:00 2001
> From: Eric Bavier <bavier@member.fsf.org>
> Date: Sun, 20 Dec 2015 16:24:24 -0600
> Subject: [PATCH 2/2] gnu: Add Asymptote.
>
> * gnu/packages/bdw-gc.scm (libgc-for-c++): New variable.
> * gnu/packages/plotutils.scm (asymptote): New variable.
> * gnu/packages/patches/asymptote-gsl2.patch: New file.
> * gnu-system.am (dist_patch_DATA): Add it.

[...]

> +;;; TODO: Remove this package once libgc is updated from core-updates.
> +(define-public libgc-for-c++
> +  (package (inherit libgc)

Please change the ‘name’ field to, say, “libgc-cxx”, so that UIs don’t
show two different “libgc” packages.

Otherwise LGTM, thanks!

Ludo’.

      reply	other threads:[~2016-01-01 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-26  2:40 [PATCH 0/2] Asymptote patches Eric Bavier
2015-12-26  2:40 ` [PATCH 1/2] gnu: libgc: Enable C++ support Eric Bavier
2015-12-27 15:54   ` Mark H Weaver
2015-12-27 11:38     ` Eric Bavier
2015-12-30 16:08   ` Ludovic Courtès
2015-12-26  2:40 ` [PATCH 2/2] gnu: Add Asymptote Eric Bavier
2015-12-30 16:11   ` Ludovic Courtès
2015-12-31 20:30     ` Eric Bavier
2016-01-01 18:10       ` Ludovic Courtès [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=87si2hgohs.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bavier@member.fsf.org \
    --cc=guix-devel@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.