Greetings,
I have some preliminary questions before even try to use guix.
My use case will be:
- Use guix on a foreign distro (Debian 12)
- Use it especially to create isolated development environment [1]
My questions:
- How easy is it to install older versions of packages? [2]
- Can I speci
On Sunday, February 9th, 2025 at 6:49 PM, Ian Eure wrote:
> The quoted part of the manual answers your question. The reason
> why this is so is that the version of a package available may
> change between channel revisions, so if you pin foobar@1.2.3, then
> `guix pull', the HEAD of the channel de
On Monday, February 10th, 2025 at 4:07 PM, Ian Eure wrote:
> Then your colleague needs to run:
>
> guix time-machine -C channels.scm -- shell -m manifest.scm
>
Ok, thank you.
Is this the official way of sharing a development shell among a
team of developers?
A couple of observation and pro
On Wednesday, February 5th, 2025 at 12:27 AM, Carlo Zancanaro
wrote:
> There are three cases here, which get harder as we go along:
>
> If the version you want is still packaged in Guix (which sometimes has
> multiple versions of a package) then this is easy: just use the version
> you want.
>
Hi all,
I would like to create a shell with pinned versions of elm and make.
Questions:
- To pin a version of a package, is it enough to use @?
- Should I put in channels information?
In the manual I read this:
If you want to “pin” your software environment to specific package
versions and vari
On Tuesday, February 11th, 2025 at 10:39 AM, Carlo Zancanaro
wrote:
> With this, it should be enough to run "guix shell -m manifest.scm" or,
> even just "guix shell" if you have an appropriate entry in
> ~/.config/guix/shell-authorized-directories.
>
Works great, thank you!
IMHO, when you wan
