From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Darrington Subject: Re: [PATCH 3/3] gnu: Add octave and dependencies Date: Sat, 25 Jan 2014 17:14:57 +0100 Message-ID: <20140125161456.GA31777@jocasta.intra> References: <1390507648-21659-1-git-send-email-jmd@gnu.org> <1390507648-21659-3-git-send-email-jmd@gnu.org> <8761p8ulih.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43562) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W75t9-000388-DT for guix-devel@gnu.org; Sat, 25 Jan 2014 11:15:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W75t4-00032f-M1 for guix-devel@gnu.org; Sat, 25 Jan 2014 11:15:19 -0500 Content-Disposition: inline In-Reply-To: <8761p8ulih.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic Court??s Cc: guix-devel@gnu.org, John Darrington --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 25, 2014 at 04:30:30PM +0100, Ludovic Court??s wrote: > + (native-inputs > + `(("gfortran" ,gfortran-4.8) > + ("perl" ,perl) > + ("less" ,less) > + ("pkg-config" ,pkg-config) > + ("texinfo" ,texinfo) > + ("ghostscript" ,ghostscript) > + ("gnuplot" ,gnuplot))) > + (propagated-inputs > + `(("texinfo" ,texinfo) > + ("less" ,less) > + ("ghostscript" ,ghostscript) > + ("gnuplot" ,gnuplot))) =20 Oh, seems like a case where native inputs need to be propagated. =20 Why do less, Texinfo, etc. need to be propagated? The octave build system is rather naive. These propagated inputs don't act= ually *need* to be present at configure/build time. But the ./configure (rather = stupidly IMO) checks for their presence, and turns off the relevant features if they are = not found. Therefore, one must declare them as native-inputs just to keep ./configure = happy AND as propagated inputs because they are called in a pipe from the octave prog= ram itself. =20 If that???s because Octave expects them to be in $PATH, then maybe an option would be to use ???wrap-program??? to wrap the ???octave??? pro= gram with a shell script that initialize $PATH to contain these. =20 That way, we make sure Octave will run with the ???right??? versions of these (those used at compile time and known to work), and the user???s environment doesn???t end up pulling them. =20 An example of ???wrap-program??? is Git (in version-control.scm.) I don't think this will work in this case, for reasons explained above. J' =20 =20 --=20 PGP Public key ID: 1024D/2DE827B3=20 fingerprint =3D 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://sks-keyservers.net or any PGP keyserver for public key. --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlLj4wAACgkQimdxnC3oJ7N3YACggeB8+BVtnfOUjSOilNmuUPTW N20Anj83HRsOwHGJ7so498vU7tx4YWsL =SmG1 -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF--