<davexunit>I opted to add the current working directory to the package search paths so that there could maybe be a 'package.scm' file in the root of a project's source tree and 'guix environment' will automagically read it.
<civodul>so package.scm would typically contain a package definition, right?
<davexunit>and then of course there's their 'sandboxing' work.
<jxself>Well, at least it's no t an official GNOME thing. That's good but sometimes I wonder if the GNOME people forget that they're part of GNU and, according to the GNU mainttainer info, are supposed to try to fit in.
<davexunit>I like GNOME as a DE, but some of these additional projects they take on seem counter-productive.
<taylanub>sandboxed "apps" with a clearly defined API for communicating with the OS about certain high-level "application" concerns[*] a la Mac OS X / iOS would be pretty great actually. [*] actually only use-case I can think of thus far is reporting "I finished initializing" to the OS
<taylanub>my family uses Ubuntu, and when I use their PC once in a while I have to notice how annoying it is to click on e.g. the Firefox icon then wait for several seconds with nothing happening on the screen, wondering if I misclicked :P
<tadni_>Is there a reason "clear" doesn't seem to ship with GNU Distro?
<tadni_>I can't seem to find it in packages either.
<jxself>Like with git if I modify a file I have to go and "git add" it again when I want to commit the change. Huh? I've already added it into version control. Having to re-add it every time makes no sense to me.
<tadni_>jxself: Yeah, I started using git for my main vc system and I found that odd.
<paroneayea>jxself: git's staging area makes a lot more sense when you start using magit :)
<davexunit>you're not adding the file, you're adding the changed hunks of that file.
*tadni_ is essentially grabbing as much guile software as possible in this config.scm
<jxself>BuTt if I have modified a file I am clearly going to want to commit the changes. The only benefit I can see is if you want to modify files not but not commit them until some as-yet-undefined future point which I don't ever want to do.
<davexunit>civodul: to what procedure(s) do I pass the values of the standard build options ('substitutes?', 'cores', etc.)? I'm not working on code now but I remember being slightly confused last night trying to identify the place where it all happens.
<davexunit>sorry if the question is silly. I can just read the code some more.