From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Allen Subject: Re: Design decision behind inputs/native-inputs/propagated-inputs Date: Thu, 21 Jan 2016 18:19:35 -0500 Message-ID: <20160121231935.GA26221@stebalien.com> References: <20160121044909.GA18348@stebalien.com> <877fj32qxy.fsf@gnu.org> <20160121160811.GA1596@stebalien.com> <56A150DD.1060207@uq.edu.au> <20160121221340.GA6151@stebalien.com> <56A15FC4.2060501@uq.edu.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59002) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMOVy-00056B-BZ for help-guix@gnu.org; Thu, 21 Jan 2016 18:19:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aMOVu-0007xd-BN for help-guix@gnu.org; Thu, 21 Jan 2016 18:19:42 -0500 Received: from mail-ig0-x235.google.com ([2607:f8b0:4001:c05::235]:35471) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMOVu-0007xZ-67 for help-guix@gnu.org; Thu, 21 Jan 2016 18:19:38 -0500 Received: by mail-ig0-x235.google.com with SMTP id t15so137416521igr.0 for ; Thu, 21 Jan 2016 15:19:38 -0800 (PST) Content-Disposition: inline In-Reply-To: <56A15FC4.2060501@uq.edu.au> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org To: Ben Woodcroft Cc: help-guix@gnu.org --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Ben, Replying back on list because I managed to take us off... On 01-22-16, Ben Woodcroft wrote: > On 22/01/16 08:13, Steven Allen wrote: > >Most distros distinguish between build dependencies and runtime > >dependencies. Guix doesn't appear to have this distinction and I am > >under the impression that it autodetects which inputs are needed at > >runtime (as apposed to at compile time only) by scanning the output > >files for references to files in the inputs. Is this not the case? > In short, no. > You could say it scans the derivation which includes a list of "runtime" > dependencies i.e. inputs and propagated-inputs. Derivations are in a > well-defined format that guix generates, and are just a way of keeping tr= ack > of dependencies that are needed at runtime. Guix doesn't scan the binaries > or shared libraries for instance. Indeed that would be mayhem as you > suggest. Thanks! That makes so much more sense. Just to be clear, given: (package (name "foo") (inputs `(("bar", bar))) (native-inputs `(("baz", baz))) ... ) If I install "foo", "foo" will **always** be able to use the files in "bar" but will not (may not?) be able to use the files in "baz"? Sorry about the confusion... --=20 Steven Allen ((Do Not Email )) --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWoWeCAAoJEGVqlrqQ0li+BG0P/jv3XP+jLgOJabTVf6gZGTOL 5Jr/zRtEQtCI92mHh9y1c//2vW8b7/L50zAwNT0CseJegY3Xq7CvP/89VNINs5jX vHI5adn1rCGokNQxXTL31rD4/NTezxkUMOZi1VufVR9WBxUTbPtnxdAM+rrOYGrz uxHhnpzM2y1JzR6AvZcEU+lCJYqJpMtPqYDHrR8ykk7UUv1hjcC6Os4ZL0uiWSBm iVApcIa0TC80NofCMIV2F5yoGVvj3dYVioo6EIzfq6AFE4eKV8spzNtTWDfcsI1I yuvsAdtKb1GCWpYVwJGpgFibaqJ5RjehwpTyFqrgDj5/qFWRaLRqjQSx9jh9zphQ F20LaqCC8jmD5UK2j1kucO/k42aNaTGAHI3+QeR+pN4e020OBIF1MiCj2wnR20vE x+IhuIN+ukhTG5TD7b+em/SbpYIMAzJTpnBU/9KpOgJHORc+rJTGToNTBy1RXjid vTaIrgGMyj9I14ylq8V+kCb1VQQlgISBT/8fdlSW7ep0z0O5Z00AX6sDPk9M8PkR GRilaTa3OOVu5tlXA8ZOgQt3qGxG266Nk2CHNFZpB85gwxzkwXN7BHnMC/I172l5 uqRLyiFWuJEdCBchtvPLtyVKxXpQh0rx0wwDUFIBcTXV7Dtw1YkYNmInZrTm67f3 dd9w2ZyiqgymP9hO8KJj =+TPK -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e--