<thomasd>yes, I'm trying to understand how it would all come together. but probably I should just play around with it
<thomasd>I'm wondering what would happen if I tried to install a package which refers to a “local” package defined in the way above.
<davexunit>thomasd: the packages that 'guix package' can see are dependent upon what packages are in guix itself in the (gnu packages ...) namespace, and the additional modules you add to GUIX_LOAD_PATH or with the --load-path flag
<thomasd>davexunit: ok, that was also my assumption
<davexunit>thomasd: you are still confusing things. a "local package" has no meaning.
<davexunit>if you want to install a package that you wrote that is outside of the guix source tree, you need to use the -L flag or set GUIX_PACKAGE_PATH appropriately
<davexunit>package objects completely capture their dependency graph, so your example of a package expression inside of a let expression is no different than any other package expression
<davexunit>there is literally nothing special about packages. I can't stress that enough.
<ng0>my question was more related to, I checkout 2 branches of an subversion repository. one currently has a (simple) guix package included, the other would need this. I think this is what the pre-inst-env etc is about, setting the environment variables
<davexunit>ng0: you would need to arrange to create a guile environment that was able to evaluate both of them
<davexunit>and be able to reference one package from the other's module
<thomasd>davexunit: how does `guix package -l` or `guix package -r` know about packages which are not defined in (gnu packages ...). Probably this information is kept in the store database (at least I think I recall there's a database there somewhere?)
<davexunit>thomasd: the store database is not involved.
<davexunit>the guix tools query all modules on GUIX_LOAD_PATH and accumulate the package objects exported from them.
<thomasd>ok, I'm going to have to login as an anonymous user before we continue this :)
<ng0>davexunit: I knew of some methods before, I'm just starting to wonder if my initial move on gnunet.org was indeed not so good and the separate package collection (for development versions) would be better
<davexunit>ng0: I don't know anything about gnunet, but if it's work that you want upstreamed then it's best to keep it in guix itself
<davexunit>thomasd: modules are first-class things in Guile, so you can programmatically traverse the symbols it exports, which is how Guix comes up with a list of all packages.
<thomasd>so if you install a package which is not in any (currently visible) module, (i.e. by evaluating a (package ...) expression, or by removing something from GUIX_LOAD_PATH), it effectively becomes invisible to tools
<mbuf>The e1000 driver is not a free software driver?
<Apteryx>Strange enough, if I just change the theme name under the .gtkrc-2.0 file, it applies the theme, but lxappearance still don't know where to look for the themes it seems. Maybe there should be an enviroment variable set which I'm unaware of.
<fr33domlover>Hello, newbie question: I use rxvt-unicode from apt-get install and it reads my configs from ~/.Xdefaults . Now I did `guix package -i rxvt-unicode` and it doesn't see that file - where do I need to place it so that Guix's rxvt sees it?
<davexunit>so for that we need a virtual networking implementation and a way to forward ports
<AlephTwo>So, I have a question: How do I remove guix without toppling my system? (it's got a large and clunky set of crap installed and guix is taking it over the edge) - alternatively, how do I remove packages from guix and re-reference the original packages without some nasty hacks?
<Common_Era>I'm here, I just don't know the answer to your question.
<AlephTwo>Fair enough. Right now, vim is my main issue - the vim binary is being sourced from the guix packages, and I really want to source my local stuff w/out having to hack through configs like a madman