From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Texlive and native-inputs Date: Wed, 29 Oct 2014 18:00:02 +0100 Message-ID: <20141029165958.GA4944@debian.eduroam.u-bordeaux.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33600) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjWbX-0006tq-2d for guix-devel@gnu.org; Wed, 29 Oct 2014 13:00:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XjWbP-0002H1-Gk for guix-devel@gnu.org; Wed, 29 Oct 2014 13:00:14 -0400 Received: from mout.kundenserver.de ([212.227.126.187]:64881) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjWbP-0002EA-6l for guix-devel@gnu.org; Wed, 29 Oct 2014 13:00:07 -0400 Content-Disposition: inline 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: guix-devel@gnu.org Currently, texlive has a certain number of native inputs: (native-inputs `(("perl" ,perl) ("pkg-config" ,pkg-config) ("python" ,python-2) ; incompatible with Python 3 (print syntax) ("tcsh" ,tcsh))) But I think these are not needed during build time, but to patch-shebang scripts that are installed into the bin directory. So should they not be normal inputs? This is part of commit c4c4cc05979f2a2d0212963c5fe1b940d63a0958 which was a mass-move from inputs to native-inputs. I wonder if these need to be verified one by one by hand? How does one know without going through every line of the build logs whether an interpreter is used during the build or in installed scripts? Or what happens if both is the case? Did I misunderstand anything? Andreas