<h0wl3vvd>Dependable. The GNU Guix package manager, in addition to standard package management features, supports transactional upgrades and roll-backs, unprivileged package management, per-user profiles, and more.
<fps>ooh, thanks for reminding me. that was a nice touch nixos had over guixsd - attribution to package creators/maintainers
<fps>with free software, attribution is often one main motivation to get people involved.. if the package definition had a author/maintainer field for the package definition itself. that might be an incentive not to be underestimated
<fps>besides giving a clue who is a good person to talk to about an issue with a particular package definition
<jroh>i don't know if i have an opinion on it, but I think fps was making the point that people like the attribution karma of being a part of a project
<codemac>I think the maintainer fields are useful for things that have complicated, not yet automated package testing
<codemac>I was thinking last night about how it would be good for us to write some amount of qualification tests so we know when things are really working as opposed to building + #:tests? #t
<codemac>Also I wish we kept around as many versions of a package as necessary, it seems like the real win of guix is possibly having recipes for just about any version of anything, (whereas what the main guix substitute builds is a matter of what guixsd packages)
<davexunit>you can have what you want by locking to specific versions of guix
<davexunit>because the inner workings of the build systems and things affect package builds, too
<davexunit>so it wouldn't be sufficient to just keep around old package recipes
<codemac>You don't need to tell me that it would be difficult, I know that. But the "rolling release" attitude plus the "functionally resolved dependencies" makes this a battle I think guix will end up fighting anyways.
<davexunit>the packages cannot exist outside of the precise version of guix that was used to build them originally
<codemac>the downgrades I was referring to aren't the same as rollbacks as the machines I allocate are dynamic, not static. It's fine though, maybe there is a workflow that makes sense that I just haven't thought out other ways yet.
***HeisenbergsDog is now known as Guest65519
***Guest65519 is now known as HeisenbergsDog
***HeisenbergsDog is now known as Guest94175
***Guest94175 is now known as HeisenbergsDog
***HeisenbergsDog is now known as Guest62916
***trisquel_ is now known as HeisenbergsDog
<jroh>do the package definitions get downloaded somewhere by default? or maybe more generally what's the workflow if I want to rebuild a particular package locally, and possibly customize it?
<apa512>does anyone know how to get sound working in icecat? specifically youtube.