unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add giac-xcas
Date: Tue, 12 Apr 2016 00:23:26 +0200	[thread overview]
Message-ID: <87a8kzbx9d.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <878u0kp805.fsf@gnu.org> (Mathieu Lirzin's message of "Mon, 11 Apr 2016 15:52:58 +0200")

Hello,

Mathieu Lirzin <mthl@gnu.org> writes:

> In fact it is public.  It is just that the module (gnu packages xiph)
> use a different convention which is to define "public" variable with
> ‘define’ and to add them to the #:export list of the module, instead of
> directly using ‘define-public’.  Either way is equivalent in Guile.

OK. Understood.

> It depends if this feature is essential for using xcas?  If yes then
> adding it as a propagated-input is still not required unless "latex,
> makeindex, ..." are used using the PATH which could not be the case
> since those programs are checked at configure time.
>
> WDYT?

I removed perl, tcsh, texlive-minimal as inputs, and tried

  guix environment --ad-hoc texlive giac-xcas --fallback -- xcas

I could preview the sheet using LaTeX. However, I sometimes got

  sh: pstopnm: command not found
  sh: pnmtopng: command not found

Not sure it is related.

Also, texlive-minimal is still in the closure, probably due to some
other input, so it doesn't reduce the size of the package.

> Looks good to me.  guix lint is happy and the build is reproducible.  I
> have modified the indentation to follow our “custom” Emacs rules.  Here
> is the updated patch.

Funnily, I broke Emacs indentation on purpose because other package
definitions in the file were disagreeing with it. I should have trusted
good ole Emacs.

> Is there a particular reason for not patching this within the
> ‘arguments’ field?

This is because the test issue is related to a given release, i.e.,
a given `source' field. OTOH, `arguments' are for control over the build
process, which is not going to change anytime soon.

To put it differently, I put the temporary fix in `snippet' and the
persistent one in `arguments'.

Moreover, you suggest to merge the two fixes into a single phase named
`fix-makefiles', which, albeit correct, is less accurate than
`patch-bin-cp'.

Anyway, this is just nitpicking; I'm fine with all the changes you made.

> Thanks and welcome!

Thank you for the review.


Regards,

-- 
Nicolas Goaziou                                                0x80A93738

  reply	other threads:[~2016-04-11 22:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 13:55 [PATCH] gnu: Add giac-xcas Nicolas Goaziou
2016-04-10 13:42 ` Nicolas Goaziou
2016-04-11 13:52   ` Mathieu Lirzin
2016-04-11 22:23     ` Nicolas Goaziou [this message]
2016-04-11 23:21       ` Mathieu Lirzin
2016-04-12 19:04         ` Nicolas Goaziou
2016-04-13 17:57           ` Mathieu Lirzin

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a8kzbx9d.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=guix-devel@gnu.org \
    --cc=mthl@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).