Hacker News Reader

Comment by Zambyte | Hacker News Reader

It is very easy to overload package versions locally for your needs, and it's quite easy to push that upstream to Guix so that others may benefit as well :)

View on HN

Can you explain (or point to an explanation) of exactly how to do that? The Guix versions of Erlang and Elixir are way out of date, and I would like to push a fix.

See here[0] for pushing a fix, here[1] for the anatomy of a package definition (often you only need to bump the version number and update the hash, but compilers may be a bit more involved). It may be useful to define package variants[2], which is what I do for some packages locally. You can also see this page[3] for using ad-hoc package variants using command line flags. Hope this helps :)

[0] https://guix.gnu.org/manual/devel/en/html_node/Contributing....

[1] https://guix.gnu.org/manual/devel/en/html_node/Defining-Pack...

[2] https://guix.gnu.org/manual/devel/en/html_node/Defining-Pack...

[3] https://guix.gnu.org/manual/devel/en/html_node/Package-Trans...

Thanks for the info, I will look into these links and see if I can push an update to Erlang and Elixir in the coming days. :)

I have patches on Guix over a year old :-)

The problem isn't contributions, it's reviews

Hm, simple version bumps tend to be outstanding for about a week for me before they are merged, and in the meantime I just add my package definition to my profile. Is there more to it than that?

I think it depends on whether the maintainers are actively using your packages or not.

I've noticed that I get fast merges if the package are popular

Check out "Guix patch review hacking session" on meetup.com: https://www.meetup.com/guix-london/events/299176148/?utm_med...

Reply on news.ycombinator.com