<vagrantc>i'm not sure if bad things happen if you mess with the files there, so i usually make a checkout somewhere else in my home dir, but maybe push/pull to/from that branch to save bandwidth and time
<vagrantc>hmmm... maybe i should just use it as the base for git worktrees...
<lfam>Thanks vagrantc... I forgot that somewhere along the line
<krafter>lfam: Ok, I now know at least what those variables include. Thanks!
*vagrantc still has somewhat fresh eyes on guix :)
<krafter>Hmm, I can't seem to be able to switch over to any virtual terminals.
<thomassgn>In a package definition, can I have some inputs use specific configure flags? I.E. get a special derivation of a package as an input? (I need ffmpeg with f.x.: --enable-libvorbis --enable-gpl)
<thomassgn>I should probably check if they are already enabled... :)
<rekado_>thomassgn: these changes sound generally useful. Could you please submit a patch for core-updates?
<rekado_>g_bor[m]: it’s a pity you’re still getting this with the latest version of shepherd.
<g_bor[m]>rekado_: I don't know what is giong on here, but I don't believe it's in shepherd. I noticed that when I start up my vm instance with default networking parameters it usually starts without problems, but as soon as I specify a nic and a hostfwd, then it fails consistently... So I believe it's a dependency problem.
<thomassgn>rekado_: cool, I'll look into it soon. Have some other packages I think I should have submitted long time ago; but will be doing some more guix work the coming weeks. :)
<matt`>rekado_: ok so let's say i want a default profile and a separate environment and i want to switch between them. i can declare the default profile with guix package --manifest=/path/to/manifest. Then, i can declare a separate environment (and switch to it) with guix environment --root=$HOME/.guix_enviro --manifest=/path/to/enviro-manifest (using --pure if i want to unset the default enironment). Now both are registered with the GC. Then
<matt`>how do i switch back to the default profile (and then back to the environment)?
<mfg>i'm asking myself a similar question matt`: when i register an environment as env, is it possible to guix environment env in some way that the GUIX_ENVIRONMENT variable contains the environemnts name?
<rekado_>mfg: the GUIX_ENVIRONMENT variable contains the name of the profile tree.
<rekado_>mfg: the environment name is ill-defined. Is it the set of all names of all packages that are part of it? Or in the case of “guix environment foo” the name “foo”?
<bzp>When reading the pdf 'guix.es.pdf', there are grammatical problems, my native language is Spanish. Could you help them?
<rekado_>matt`: you can “enable” a profile by running this: GUIX_PROFILE=/the/profile; source $GUIX_PROFILE/etc/profile
<bzp>I'm not computer, just a user and enthusiast who admires the work that the FSF, GNU and GUI does.
<PirBoazo>rekado : in operating-system after host-name and before users declaration.
<wingo>humm who is responsible for the spanish translation of the manual? is it the translation project?
<bzp>I really like guixsd, I suggest that you can make support for old PC equipment
<mfg>rekado_: I'm not sure what you mean... the command itself is obviously wrong, yes. But i mean if i can have something else in the GUIX_ENVIRONMENT var, say GUIX_ENVIRONMENT="devel" instead of the envs store path ?!
<rekado_>PirBoazo: the field name is “groups”. The value for that field must be a list of values created with the “user-group” constructor.
<rekado_>mfg: the variable cannot be changed (without changing the code obviously). Why would you like something like “devel” to be there?
<rekado_>mfg: if that’s for a shell prompt you could do that by just looking if GUIX_ENVIRONMENT is set.
<rekado_>bzp: could you please send an email to firstname.lastname@example.org with a list of the grammatical errors? (Are these mistakes in Spanish as used in Spain or as used in other countries?)
<PirBoazo>rekado : in 8.5 User Accounts § : User group declarations are even simpler:
<str1ngs>Ports based distro's are good if you have exotic hardware. Or you have highly specialized server deployment.
<ng0>that's a weird assertion. not the last, the first. ports trees have nothing to do with hardware.. well they start to do on some systems, but i think you were just generalizing.
<str1ngs>maybe, but I don't personally find the idea of rebuilding the world fun. it's resource intensive and redundant. Especially on low end hardware like laptops :P
<ng0>still has nothing to do with exotic hardware. and some ports trees have tools and infrastructure now for a long time which enable binary only installations (see for example freebsd).
<str1ngs>sure because even freebsd, understands that it's pointless to rebuild every package on every machine with no benefit. The only place it has benefit is when you have exotic hardware and use cases.
<str1ngs>even on Guix it does not make sense for every machine to be rebuilding packages. If that was the case why put so much effort into repeatable builds. Unless the end goal is to actually reuse those builds..
<ng0>i have to continue looking intoi server replcament to buy. i have different ideas, but i respect yours and have too much of a grumpy day to go into detail (my only test system died)
<str1ngs>I think you took my statement as ports system are only for exotic hardware. What I meant was exotic hardware benefits the most.
<ng0>i hate buying new hardware. this was 10 years old or so. much older systems were still running at this point. so I can get a 1000+ euro silent'ish desktop or a 250 euro server.
<b0f0>contribute, how do I do that. I have this problem that if I want to help fix stuff I dont have an idea how to do that, all at such a high level of thiking. But always had an idea in my head that I want to give back - contribute. I guess I could try writting a package or somthing easy . What does #guix think, where should a noob start ?)
<b0f0>I subscribed to help-guix and discussion too
<b0f0>dongcarl: why would I install guix again ? It's installed. I mean I trying to understand what you just wrote. checkout branch must be a git command, I guess you are downloading/pulling all of guix to some "directory". Then ywhat you want with guix environment guix is to enable dev tools and the evironment to build stuff, then play with guix and the try to compile that and istall. Is that what you were thinking
<dongcarl>rekado_: Hard problem to solve, especially in a rapidly-growing project like Guix. I wish there was a labelling system so that maintainers could label patches with priority to ease other reviewers
<sebboh>hi again all. Let's say I author some config.scm and then I do `guix system init ...`. Then I boot into the new system and install a package. How may I get a copy of my *new* config.scm, which should contain that package I just installed?
<str1ngs>sebboh: you can add this as a service. (simple-service 'config-file etc-service-type`(("config.scm" ,this-file)))
<str1ngs>guix system init kinda implied system configuration. umm was I wrong in my understanding?
<sebboh>Maybe I'm asking the wrong question. Can I keep my config for my guix system in version control, and if I do so, which things might escape version control? (I guess `guix install emacs` wouldn't get recorded anywhere unless I "export" my package list somehow.)
<sebboh>str1ngs: it's likely that *I* am wrong in my understanding. I just got here. :)
<str1ngs>sebboh: you can keep your system config.scm in version control. just reffer to that file when using guix system
<eric23>I am a little confused. I just installed guix 1.0.1 in the graphical installer. I see the instructions to do "guix pull && sudo guix system reconfigure /etc/config.scm", but it gives me a warning that guix pull was never run. I thought I was to run guix pull as my user not root.
<eric23>"guix system: warning: /root/.config/guix/current not found: 'guix pull' was never run"
<str1ngs>sebboh: so you could keep config.scm and profile.scm in version control. and just refer to those files. when using guix system and guix package. no caveat's in terms of version control. I hope that answers your question.
<vagrantc>eric23: you might want: sudo -E guix system ...
<vagrantc>eric23: then it will use your user's "guix pull"
<vagrantc>eric23: otherwise, you'll need to also run "guix pull" as root.
<str1ngs>jje: check guix system --help for exact syntax pleaase
<sebboh>ngz, yes. You need to start the guix daemon. I had to google the command line, and I ended up burning a virtual console for it, so, you probably don't want the specific invocation I used anyway.
<ngz>The guix daemon is already started, as a systemd service (or whatever this is called).
<ngz>Yes, and systemctl tells me it is active. I tried to restart it, too.
<sebboh>ngz, well, I'll get out of the way in case some more experienced person can help where I cannot. My next step is to poke around with `ps` and `lsof` to see if the guix daemon is indeed running and if it has some socket file open at some other location. But that's just poking in the dark.
<rekado_>pretty much everything ends up somewhere in the store; some things are “checked out” at boot time to populate /etc, but only in cases where the software is not flexible enough to tell it to look elsewhere.
<sebboh>wait, is there some simple way to get a guile repl that has all these guix functions defined so I can just eval some of these service definitions and see what comes out, perhaps pretty-printed if I can figure out how to do that in scheme? I'm an amateur common lisp hacker. (Amateur!)
<rekado_>ngz: I guess you may be able to work around this by setting NIX_STORE_DIR, but be careful!
<rekado_>ngz: I’m trying to reproduce this but haven’t been successful yet.