unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: sbaugh@catern.com
To: guix-devel@gnu.org
Subject: Re: Developing libraries for the GNU system with Guix
Date: Fri, 14 Oct 2016 09:56:25 -0400	[thread overview]
Message-ID: <874m4fjapi.fsf@catern.com> (raw)
In-Reply-To: 87bmynaxud.fsf@gnu.org

ludo@gnu.org (Ludovic Courtès) writes:
> sbaugh@catern.com skribis:
>> - Currently every dependency is located at a well known globally unique
>>   and globally meaningful path; add some kind of "variant package"
>>   construct which specifies a package which is "passed in" to the
>>   environment (maybe by bind-mounting it in a filesystem namespace;
>>   implementation specifics aren't important). To put this in a
>>   programming language sense, one of these packages being present would
>>   turn a Guix distribution from a value into a function.
>
> Not sure I understand.  What do you mean by “passed in to the
> environment”?

I just mean that this would be a path that is not necessarily pointing
to a directory containing the files desired by other packages depending
on it. To make a complete functioning system, the path would need to be
pointed at something containing the right files. (something of the right
type) It could be pointed at different directories in different
filesystem namespaces, and that "pointing" would happen outside the
filesystem namespace when the namespace is created.

  reply	other threads:[~2016-10-14 13:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13 23:57 Developing libraries for the GNU system with Guix sbaugh
2016-10-14 13:01 ` Ludovic Courtès
2016-10-14 13:56   ` sbaugh [this message]
2016-10-14 18:58   ` Ricardo Wurmus
2016-10-17 22:04     ` Ludovic Courtès
2016-10-18  6:16       ` Ricardo Wurmus
2016-10-18 12:45         ` Ludovic Courtès
2016-10-23 14:12       ` sbaugh

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=874m4fjapi.fsf@catern.com \
    --to=sbaugh@catern.com \
    --cc=guix-devel@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).