unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Fis Trivial <ybbs.daans@hotmail.com>
Cc: 30093@debbugs.gnu.org
Subject: bug#30093: Installing python-ipython breaks Gnome on Fedora.
Date: Sun, 14 Jan 2018 16:45:01 -0800	[thread overview]
Message-ID: <87po6cc5ma.fsf@gmail.com> (raw)
In-Reply-To: <876084dqmr.fsf@gmail.com> (Chris Marusich's message of "Sun, 14 Jan 2018 14:25:48 -0800")

[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]

Chris Marusich <cmmarusich@gmail.com> writes:

> Of course, if there is a way to solve this class of problem more
> generally without introducing impurities, that'd be great.  I just can't
> think of one at this time.

There is existing code in Guix that puts things into the store which
depend on things outside of the store.  The specific examples I know of
are:

- When Guix downloads source files from the Internet and puts them into
  the store.

- When Guix finds Guile modules in the GUILE_LOAD_PATH and puts them in
  the store, as a result of using 'with-imported-modules' with a
  G-Expression.

- Other code that exists explicitly to add files to the store, such as
  the 'local-file' procedure.

In these cases, what winds up in the store ultimately comes from the
outside world.  I'm not 100% sure, but I think that when something from
"outside" is put into the store in this way, it's done outside the scope
of a derivation, since derivations should only be able to access files
that exist in the store.

Anyway, this means that technically, we probably could come up with a
solution that takes the current value of an environment variable and
ultimately incorporates it into a build that creates the new profile
generation.  However, it doesn't change the fact that this class of
problem will probably continue to occur on foreign distributions, so I
still think it might be best to deal with the problems on a case by case
basis.
  
-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-01-15  0:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 21:32 bug#30093: Installing python-ipython breaks Gnome on Fedora Fis Trivial
2018-01-13 21:39 ` Fis Trivial
2018-01-14  0:36   ` Chris Marusich
2018-01-14 18:31     ` Fis Trivial
2018-01-14 19:01       ` Fis Trivial
2018-01-14 22:25       ` Chris Marusich
2018-01-15  0:45         ` Chris Marusich [this message]
2018-01-17 19:53           ` Fis Trivial
2020-10-04 18:25             ` Maxim Cournoyer
2021-05-19 16:14 ` bug#30093: what manual workaround? tomas.almeida
2021-05-24  0:16   ` Carlo Zancanaro
2021-05-24 10:30     ` tomas.almeida
2022-09-29  2:50   ` bug#30093: Installing python-ipython breaks Gnome on Fedora Maxim Cournoyer

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=87po6cc5ma.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=30093@debbugs.gnu.org \
    --cc=ybbs.daans@hotmail.com \
    /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).