From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pjotr Prins Subject: Re: [PATCH] Add python2-seqmagick. Date: Mon, 21 Sep 2015 09:34:32 +0200 Message-ID: <20150921073432.GA31971@thebird.nl> References: <55FAA83C.3040403@uq.edu.au> <55FD2C91.9080203@uq.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49232) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZdveV-0005Fg-C4 for guix-devel@gnu.org; Mon, 21 Sep 2015 03:36:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZdveR-0004M1-AA for guix-devel@gnu.org; Mon, 21 Sep 2015 03:36:43 -0400 Received: from mail.thebird.nl ([95.154.246.10]:45695) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZdveR-0004KZ-4G for guix-devel@gnu.org; Mon, 21 Sep 2015 03:36:39 -0400 Content-Disposition: inline In-Reply-To: <55FD2C91.9080203@uq.edu.au> 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: Ben Woodcroft Cc: "guix-devel@gnu.org" This contains the most lucid description of 'inputs' I have yet seen. Could they go into the main Guix documentation? Pj. On Sat, Sep 19, 2015 at 07:36:17PM +1000, Ben Woodcroft wrote: > On 18/09/15 01:51, Ricardo Wurmus wrote: > > Hi Ben, > > thank you very much for your patch! > > and you sir, for the review. > > + (inputs > + `(("python-setuptools" ,python2-setuptools) > > I think this should be a native input instead. > > ok > > + ("python-biopython" ,python2-biopython))) > > And this looks like it should be a propagated input instead. Have you > tried running seqmagick after installing it with this package recipe? I > found that Python executables often require either propagated inputs or > wrapping in PYTHONPATH to work without runtime errors. > > I did, although not well enough to pick up the error you point out. > Actually I'm a bit confused as to the difference between the input types > even after reading the manual. Is this a fair summary? > > native-inputs: required for building but not runtime - installing a > package through a substitute won't install these inputs > inputs: installed in the store but not in the profile, as well as being > present at build time > propagated-inputs: installed in the store and in the profile, as well as > being present at build time > > Anyway, it seems as if the package would have worked because a wrapper is > generated with PYTHONPATH including inputs, propagated-inputs and > native-inputs. But this seems a bit strange - why would native inputs be > in the runtime wrapper? > $ cat /tmp/a.fa > >a