Hi,
- Do Guix developers just hack in ~/src/guix, add their own
packages/updates, and commit them later? in this case:
- How do they deal with channel authentication, merges, and rebasing
with Guix’s master branch?
- Is there anything like git bisect but for guix channel? so I can get
what commit (in guix) broke my channel and know how to fix it.
- How to deal with broken package builds? They are catched by the CI
system: should be report them? why doesn't guix maintain a develop
branch and use master for changes that pass CI?
Any tips or suggestions would be greatly appreciated because I’m stuck
trying to maintain my workflow without constantly running into problems
after updating Guix.
* CONTEXT
I've been using Guix for 3 years now, I really like it, but every time I
try to update, some package I use does not build or some API change and
my custom channel stops working. I mainly use Emacs, EXWM, Firefox,
KDEConnect, and LibreOffice.
My own channel: consists of custom Emacs builds (from master), some
(emacs and not emacs) packages not in guix and a procedure to built
emacs packages with custom emacs versions. A few weeks ditched it
because couldn’t fix my channel with new changes in guix. Now using
gs-101/emacs-master and the built-in Emacs package manager with
package-vc-install.
I am dissapointed for not being able to use guix, but also (now) I don't
see the for Emacs because with use-package and :vc I can even share my
Emacs config with non Guix systems without problems.
At this point I’m even considering switching to another distro for my
desktop (I don’t have this many problems on servers, I don't do anything
special there and have automatic upgrades). *But I’m wondering... I’m
missing something in the development process or are my skils are not
enough for Guix*.
Thanks in advance!
