• 0 Posts
  • 64 Comments
Joined 3 years ago
cake
Cake day: July 22nd, 2023

help-circle

















  • I wanted to learn more about my system. But I felt like Debian and similar distributions where kind of hardcoded systems and that made the whole OS like a blackbox myth. I thought about Gentoo but I didn’t felt like having to track different configuration and building steps in my head in order to remember what system I had built. I do even struggle to remember how the fuck I did setup my WM in my Debian system.

    Long time ago I also had discovered Guix from the FSF distro list (who hasn’t check that site in some spare time, right?). At the time it felt like the impossible distribution for me. A year and a half ago, with more knowledge in my bag I decided to build my own fully free software laptop by using an X220 Thinkpad (which has the old ME that can be totally disabled), since I wanted to go full tryhard I decided to pick what I felt it was the most obscure fully free software Distro at the time. After discovering what Guix was capable to do I remember thinking why no one has ever thought about this? This is genius! (I did not know about NixOs at the time)

    Having the power of building a reproducible OS that is described with a recipe is amazing. How many times I went into rescue mode for touching things I shouldn’t with Debian? With guix I just rollback my system to a previous description and we are good to go. Guix also is pioneering the full source bootstrap concept which also sounds like something we should really have in our machines. Package descriptions that give you a recipe about how it should be built. And now you can even have a whole description of your home configuration environment! I won’t get lost when configuring WMs or my bash!

    Conceptually it feels elegant and the correct way to build distributions and any software collection in general! Having both the build scripts and definitions written in Guile Scheme is much more convenient than having to embed DSL code like Nix approach. Lisp S-expresions literally feel built for that purpose.

    It is still a young distro, documentation is lacking in some aspects but everybody in the community is passionate about.



  • QT uses one or another, either GPLv3/LGPLv3/GPLv2 or privative. Poisoning open source? If you refer to the fact that they allow a closed source licence, yes I also dislike that. But how is GPLv3 poisoning anything? If you want to use and modify/contribute to the QT project then you have to maintain user freedoms unless you pay QT for their rights. In the end term, the user is always respected since contributions to base qt are always free software. With only a GPL licence then the developers would need to share source code for their distributions. The Multiple-Licence allows third party developers to gain “fully-paid-ownership” which allows them to close source it.

    Also since QT it’s allowed to be shiped with LGPL third party devs can close source their parts of code that link against QT.

    So it’s basically an interesting way of having a permissible licence while keeping the QT base fully libre.

    Probably you refer to the availability that open source philosophy gives. Yeah, that is the principal difference between libre software and open software. Open software advocates for fully openness for the sake of the developers no matter what they want to make later with it, libre software advocates for the source code of the end user.