Gregory's Server@dthompson I just mean that it’s like enabling “non-free” in Debian: now ‘guix search’ turns up both free and proprietary things.
|
6 comments
@dthompson @civodul nixos has an interesting feature for this case: nixpkgs.config.allowUnfreePredicate You can then effectively whitelist only the packages you require and still get an error for everything else Would something similar be useful for nonguix?   @aheaume @dthompson To be honest, I don’t find Nixpkgs’ handling of non-free software “interesting” at all. I contributed to Nixpkgs for ~4y. At the time, anything could get in Nixpkgs, free or not, and licensing info was often missing and was not reviewed, etc. Thus, as a user, if you chose to use only free software, you could hardly trust it to DTRT. I think mixing free and non-free in the same repo and in the same project is a big mistake. @civodul @dthompson I don’t have an opinion on how free/non-free repos should be handled, but I admire your stance and appreciate it. I’m new on Guix and even though the Guix Manual and Cookbook are amazingly written, do you think it’d be good idea for a wiki page mostly to explain how some packages work(or additional tips in the /packages page)? For example emacs-exwm looks for .exwm file otherwise loads exwm-default-config etc. Would be helpful to new users @apo11o The project accepts contributions to the Cookbook in any form! If there are tip and tricks that you think ought to be documented, please propose a new Cookbok section. If differs from a typical wiki in that we collectively will take care of keeping it up-to-date, removing outdated info, and so on. |
@civodul ah, thanks for clarifying. I definitely don't love that. If I could filter the channel to only contain the couple of packages I use then I would. guix search clearly points to where they are from, at least.