5 ms·

Not true. You can write your own packages in the same high level interface. Including the mainline Linux kernel and broadcom drivers. I have GuixSd running o

Not true. You can write your own packages in the same high level interface. Including the mainline Linux kernel and broadcom drivers. I have GuixSd running on my 2013 MBP

tacolizard 8y ago
can you tell me how you got that running in some more detail? I also have a 2013 MBP and would like to try out GuixSD
- serhart 8y ago
  I don't have access to it now. When I do I can put the package definitions and OS config up somewhere. When you first boot GuixSD most of the core stuff should work fine. Wireless will not work but you should have ethernet. I created mainline linux kernel and firmware packages [1]. Then you need to get the broadcom b43 firmware to get wireless support. I think I made 2 packages. One for b43-fwcutter and one the broadcom-wl firmware which uses b43-fwcutter to cut and install it. I think just about everything on my MBP was working after that. [1] example linux package https://github.com/wingo/guix-nonfree/blob/master/gnu/packages/linux-nonfree.scm https://github.com/wingo/guix-nonfree/blob/master/gnu/packag... [2] http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/ http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/
- serhart 8y ago
  Here is a gist of the relevant packages and configs I have for my MBP. https://gist.github.com/steve-ayerhart/81c9dfc773472e08002cd890216de481 https://gist.github.com/steve-ayerhart/81c9dfc773472e08002cd...
noobermin 8y ago
Is there a...non official repository of these somewhere?
- serhart 8y ago
  None that I know of currently. The OS is version 0.15.0. It's very young and doesn't have a huge user base. I'm sure there will be non gnu repositories that will eventually spring up. I've even toyed with the idea of setting one up.
  - nerdponx 8y ago
    Even as a toy example, a blog post and code that demonstrates setting up a 3rd-party package repository would be helpful. I'm just afraid of the GUIX team deciding they don't want to support 3rd-party repos because it encourages non-free software use, and deliberately stonewalling development of related features.
    - rekado 8y ago
      Guix has had support for external package definitions for a long time (via GUIX_PACKAGE_PATH) and recently gained a channels feature, which makes this even easier. At the institute where I work we use this feature to provide package variants that aren't going to be added to Guix proper (e.g. because they are no longer supported upstream or because they are only useful on obscure systems). This mechanism can be used to include package definitions for non-free software, of course, but this doesn't mean that the Guix project encourages the use of non-free software. You have the freedom to package up and use non-free software, but we won't make them part of Guix, build them on our build farms, and we won't hold back changes to the mechanism even if that might break 3rd-party collections of non-free software. You don't really need a blog post about how to set up a package repository, because it's right there in the Guix manual. PS: It's "Guix", not "GUIX" ;)
      - nerdponx 8y ago
        Thanks for the reply. As long as it's easy to mix free and non-free packages at my discretion, I'm willing to give it a shot. Also, thank you for the capitalization correction. It grinds my gears when people capitalize things unnecessarily and I wouldn't want to be one of them!

Not true. You can write your own packages in the same high level interface. Including the mainline Linux kernel and broadcom drivers. I have GuixSd running on my 2013 MBP

tacolizard 8y ago

can you tell me how you got that running in some more detail? I also have a 2013 MBP and would like to try out GuixSD

serhart 8y ago
I don't have access to it now. When I do I can put the package definitions and OS config up somewhere. When you first boot GuixSD most of the core stuff should work fine. Wireless will not work but you should have ethernet. I created mainline linux kernel and firmware packages [1]. Then you need to get the broadcom b43 firmware to get wireless support. I think I made 2 packages. One for b43-fwcutter and one the broadcom-wl firmware which uses b43-fwcutter to cut and install it. I think just about everything on my MBP was working after that. [1] example linux package https://github.com/wingo/guix-nonfree/blob/master/gnu/packages/linux-nonfree.scm https://github.com/wingo/guix-nonfree/blob/master/gnu/packag... [2] http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/ http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/
serhart 8y ago
Here is a gist of the relevant packages and configs I have for my MBP. https://gist.github.com/steve-ayerhart/81c9dfc773472e08002cd890216de481 https://gist.github.com/steve-ayerhart/81c9dfc773472e08002cd...

noobermin 8y ago

Is there a...non official repository of these somewhere?

serhart 8y ago
None that I know of currently. The OS is version 0.15.0. It's very young and doesn't have a huge user base. I'm sure there will be non gnu repositories that will eventually spring up. I've even toyed with the idea of setting one up.
- nerdponx 8y ago
  Even as a toy example, a blog post and code that demonstrates setting up a 3rd-party package repository would be helpful. I'm just afraid of the GUIX team deciding they don't want to support 3rd-party repos because it encourages non-free software use, and deliberately stonewalling development of related features.
  - rekado 8y ago
    Guix has had support for external package definitions for a long time (via GUIX_PACKAGE_PATH) and recently gained a channels feature, which makes this even easier. At the institute where I work we use this feature to provide package variants that aren't going to be added to Guix proper (e.g. because they are no longer supported upstream or because they are only useful on obscure systems). This mechanism can be used to include package definitions for non-free software, of course, but this doesn't mean that the Guix project encourages the use of non-free software. You have the freedom to package up and use non-free software, but we won't make them part of Guix, build them on our build farms, and we won't hold back changes to the mechanism even if that might break 3rd-party collections of non-free software. You don't really need a blog post about how to set up a package repository, because it's right there in the Guix manual. PS: It's "Guix", not "GUIX" ;)
    - nerdponx 8y ago
      Thanks for the reply. As long as it's easy to mix free and non-free packages at my discretion, I'm willing to give it a shot. Also, thank you for the capitalization correction. It grinds my gears when people capitalize things unnecessarily and I wouldn't want to be one of them!