Hi,
Thanks for sharing.
On Mon, 26 Sep 2022 at 14:30, Olivier Dion via "Development of GNU Guix and the
GNU System distribution." <guix-devel@gnu.org> wrote:
> dev-env:
> --8<---------------cut here---------------start------------->8---
> #!/bin/sh
> guix shell \
> --pure \
> dyninst \
> gdb \
> git \
> guix \
> lcov \
> guile-quickcheck \
> perf \
> lttng-ust \
> lttng-tools \
> --development libpatch \
> -- $@
> --8<---------------cut here---------------end--------------->8---
>
> Note the latest script where I have development packages for libpatch,
> but also other utitilies that are good to have for developer.
Well, I am not happy with my workflow but I have something similar for
some projects. However, instead of this list, I have a “general” script
(named guixify) under ~/.local/bin/ which roughly reads:
--8<---------------cut here---------------start------------->8---
#!/bin/sh
guix time-machine -C channels.scm \
-- shell --pure \
-m manifest.scm \
-- $@
--8<---------------cut here---------------end--------------->8---
where manifest.scm and channels.scm are kept with the Git project. I
prefer to pin a specific Guix revision to avoid bad surprises. :-) Well,
in a project, I just run:
guixify make # run make using the Guix environment
guixify # enter in the environment
I thought to write an extension but I am not convinced by the interface
I want. :-)
Cheers,
simon
