***civodul changes topic to 'GNU Guix | http://gnu.org/s/guix/ | http://www.fsf.org/news/fsf-adds-guix-system-distribution-to-list-of-endorsed-distributions | 0.8.2 is in the works! | This channel is logged, see <https://gnunet.org/bot/log/guix>.'
<davexunit>I'm writing a deployment tool that abstracts away the details of manipulating any particular "platform". so that you can use the same tool to manage VMs, physical hosts, containers in the future, perhaps things in an OpenStack "cloud"
<freaj>you need a word to designate the kind of "physical hosts/vm/whatever" ?
<mark_weaver>I'm really amazed that we've gone so long without something like this. I guess that civodul's machine never crashes, or something :)
<mark_weaver>one of our key features is supposed to be that you can (almost) always rely on being able to boot into an older system if the newest one fails, but this problem undermines that, and leaves people with systems that won't boot properly no matter what profile they try to boot into.
<mark_weaver>honestly, I think we should just apply the patch I just cited for now, if no one has the time to make a better one.
<mark_weaver>notes about setting it up: (1) you also need 'wicd' in the list passed to 'dbus-service', (2) 'wicd' should probably be in your system-wide profile, and (3) add 'netdev' to your user's supplementary-groups
<mark_weaver>with those things, you should be able to run 'wicd-gtk' from within your X session to configure networking.
<davexunit>oh it won't do a wired connection automatically?
<joehillen>well, then look at it this way, he's demonstrated that there is at least some market for a consumer product that promotes freedom. now all somebody needs to do is actually create something that delivers on its promise
<fchmmr>He sold it, now it's not run by him anymore.
<fchmmr><joehillen> well, then look at it this way, he's demonstrated that there is at least some market for a consumer product that promotes freedom. now all somebody needs to do is actually create something that delivers on its promise
<mark_weaver>yeah, it's the false claims that I find the most objectionable
<mark_weaver>I don't think the librem is promoting freedom. instead, it's tempting people to abandon their software freedom, by choosing librem instead of machines like the Libreboot X200 that really can be run without several megabytes of blobs and backdoors.
<df_>it's pretty much cashing in on people's desire for free hardware
<joehillen>personally I don't see a problem since the code doesn't live in the Guix repo, but the packaging/build instructions do. is that incompatible with FSDG? preventing me from installing proprietary software?
<mark_weaver>however, guix is designed to be hackable, so it's easy to add your own stuff in your private branch
<davexunit>since proprietary software cannot be built with our toolchain, it can never be reproducible, and users would have to trust a third party.
<fchmmr>joehillen, yes, that is what you have to do.
<fchmmr>If you want proprietary software, you'll have to fork Guix. Guix upstream will never accept proprietary software, or software that encourages proprietary addons, or scripts (metadata) that download and build proprietary software, etc.
<davexunit>one of the technical goals of guix is to ensure that no one has to trust a single third party for binaries
<fchmmr>is it me, or does #guix have more people in it than #trisquel?
<rekado>joehillen: at work some people use a few applications that impose non-commercial restrictions; GUIX_PACKAGE_PATH is sufficient for these cases. The Guile module containing those recipes is completely separate from the Guix repo.
<rekado>I should say, though, that some developers are even willing to consider relicensing. (Already two agreed to a license change, but haven't yet made their decision public/quotable.)