Re: Did nmap just become non-free?

[zimoun]

Hi Marius,

On Thu, 15 Oct 2020 at 00:13, Marius Bakke  wrote:

> > This is definitely not a consistent license for us.
>
> Having re-read the original text (without the annotations), the thing
> that stands out is:
>
>   Proprietary software companies wishing to use or incorporate Covered
>   Software within their programs must contact Licensor to purchase a
>   separate license. Open source developers who wish to incorporate parts
>   of Covered Software into free software with conflicting licenses may
>   write Licensor to request a waiver of terms.
>
> From .

IANAL, it’s a weird way to "double" license; it’s fine since it’s GPLv2
too.


> I'll see what licens...@fsf.org has to say first.

For the record, the free GNU/linux distributions Parabola (listed here
[1]) distributes "nmap": 

   

It will be interesting to know what FSF licensing will say.


> PS: Licenses make terrible bed-side reading!

Boring enough to want to sleep fast? ;-)


All the best,
simon

Re: Specifying dependencies among package outputs?

[Brett Gilio]

Simon South  writes:

> Am I right in thinking there is no way to specify dependencies among the
> outputs of a single package? To specify that a package's "out" output
> depends on its "lib" output, for instance.
>
> I ask because the Knot package (in gnu/package/dns.scm) builds a number
> of logically distinct targets---daemon, libraries, administrative
> utilities, general-purpose utilities, and documentation---and it would
> be nice to separate at least some of these into individual outputs, in
> part because we could then specify only the libraries as a dependency of
> Knot Resolver.
>
> However, Knot's daemon and utilities have the same dependency on its own
> libraries, so pulling those into a separate "lib" output would be liable
> to break everything else.
>
> I've searched and can't find an example of this being done, nor can I
> find any mention of it in the documentation. So I assume it's simply not
> possible, and you would need to define an entirely separate package that
> builds from the same source code---right?

Unless I am mistaken, this is not possible. When using a specific
output, it still fetches the entire package closure. But only that
specific output propagates to the profile. Adding an output as a
dependency would surely cause a non-termination situation with the
interpreter.

I have cc'ed guix-devel as I think that is the better fit for this
question.

Best


-- 
Brett M. Gilio

https://brettgilio.com

Re: Did nmap just become non-free?

[Brett Gilio]

Marius Bakke  writes:

> Having re-read the original text (without the annotations), the thing
> that stands out is:
>
>   Proprietary software companies wishing to use or incorporate Covered
>   Software within their programs must contact Licensor to purchase a
>   separate license. Open source developers who wish to incorporate parts
>   of Covered Software into free software with conflicting licenses may
>   write Licensor to request a waiver of terms.
>
> From .
>
> So a "proprietary software company" cannot use or incorporate nmap
> within a program, even if that program is free (as in software)?

I believe that clause about "proprietary software companies" (if such a
thing could even be defined, legally) violates freedom 0.

Do let me know what the licensing lab says.

-- 
Brett M. Gilio

https://brettgilio.com

Re: Did nmap just become non-free?

[Marius Bakke]

Brett Gilio  writes:

> Marius Bakke  writes:
>>
>> ...I'm fairly certain this is not an acceptable license for Guix, or
>> free software distributions in general.
>>
>
> This is definitely not a consistent license for us.

Having re-read the original text (without the annotations), the thing
that stands out is:

  Proprietary software companies wishing to use or incorporate Covered
  Software within their programs must contact Licensor to purchase a
  separate license. Open source developers who wish to incorporate parts
  of Covered Software into free software with conflicting licenses may
  write Licensor to request a waiver of terms.

From .

So a "proprietary software company" cannot use or incorporate nmap
within a program, even if that program is free (as in software)?

>> So I think we should revert the license change, as well as the update
>> to 7.90 which introduced the new license.
>>
>> Now to read the previous license text, perhaps that will help me sleep..
>>
>
>
> As to how to fix it, I think we will need to revert the change, and also
> make note of the FINAL version of nmap that was still compliant with FSDG.

I'll see what licens...@fsf.org has to say first.

PS: Licenses make terrible bed-side reading!


signature.asc
Description: PGP signature

Re: [BLOG] Childhurds and GNU/Hurd substitutes

[zimoun]

On Wed, 14 Oct 2020 at 22:57, Jan Nieuwenhuizen  wrote:

> >> It's tricky; --target is != --system: --target is a cross-build.  IOW,
> >> --system => (%current-system), --target => (%current-target-system).

[..]

> Yeah, this can be confusing.  The target is a triplet
> (https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Specifying-Target-Triplets.html),
> e.g.  i586-pc-gnu, x86_64-unknown-linux-gnu; system is specified by the
> platform, or interpreter name; see e.g. gnu/packages/bootstrap.scm:
> glibc-dynamic-linker for a list of platforms.

Ah ok!  Sorry, you already told me: --target != --system.  Just previously.

Well, the Zen of Python (python -c 'import this') seems appropriate
here: "Although that way may not be obvious at first unless you're
Dutch".  :-) Even if it is only inherited from autoconf. :-)

Cheers,
simon

Re: [BLOG] Childhurds and GNU/Hurd substitutes

[Jan Nieuwenhuizen]

zimoun writes:

Dear Simon,

> Thank you for the help!  I have fun. :-)

Good!

> On Wed, 14 Oct 2020 at 16:15, Jan Nieuwenhuizen  wrote:
> I do not know if it was bad luck or if "herd start ssh" does the trick
> but here we go! \o/
>
> $ ssh -p 10022 root@localhost
> The authenticity of host '[localhost]:10022 ([127.0.0.1]:10022)' can't
> be established.
> ECDSA key fingerprint is SHA256:iETZ8thOyFqk+35g02tRW9FRzLqilgYYlxWr/9xn/kI.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added '[localhost]:10022' (ECDSA) to the list of
> known hosts.
> 
> 
>   This is the GNU Hurd.  Welcome.
>
> Thank you.

\o/

>> > Last, I am confused:
>> >
>> >debian$ guix build hello --target=i586-pc-gnu hello
>> >/gnu/store/09sz4qsqp3zgnbaxhzppspaxihwmfzll-hello-2.10
>
> [..]
>
>> It's tricky; --target is != --system: --target is a cross-build.  IOW,
>> --system => (%current-system), --target => (%current-target-system).
>>
>> So,
>>
>> guix build hello --system=i586-gnu hello
>>
>> should give the identical hash.
>
> What is the target?  i586-pc-gnu or i586-gnu?  The blog post mentions
> 'i586-pc-gnu' at the beginning and then 'i586-gnu'.  I suppose it is
> 'i586-gnu' since using this target produces the expected hash.
> What do I miss?

Yeah, this can be confusing.  The target is a triplet
(https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Specifying-Target-Triplets.html),
e.g.  i586-pc-gnu, x86_64-unknown-linux-gnu; system is specified by the
platform, or interpreter name; see e.g. gnu/packages/bootstrap.scm:
glibc-dynamic-linker for a list of platforms.

Greetings,
Janneke

-- 
Jan Nieuwenhuizen  | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

Re: Removing/replacing “Guix in action” video from the home page?

[Joshua Branson]

Well, I've created a basic guix package management video.  It's about 7
minutes long.  You'll notice I made it a little goofy.  Essentially
building the XDG mime database takes a while.  So I just read from
Stallman's essays during the downtime.

If someone wants to show me how to install packages without having to
wait so long for the xdg mime database to build, please let me know, and
I'll re-make the video.

https://video.hardlimit.com/videos/watch/c0dfb36a-a84b-4363-8b1b-17aeadd4aaaf

Thanks,

Joshua

--
Joshua Branson
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
"You can have whatever you want, as long as you help enough other people get 
what they want." - Zig Ziglar

Re: [BLOG] Childhurds and GNU/Hurd substitutes

[zimoun]

Dear Janneke,

Thank you for the help!  I have fun. :-)


On Wed, 14 Oct 2020 at 16:15, Jan Nieuwenhuizen  wrote:

> > Using this command line (from gnu/system/examples/bare-hurd.tmpl):
> >
> > guix environment --ad-hoc qemu \
> >  -- qemu-system-i386 -enable-kvm -m 512  \
> >   -device rtl8139,netdev=net0 -netdev 
> > user,id=net0,hostfwd=tcp:127.0.0.1:10022-: \
> >  -snapshot -hda \
> >  $(guix system disk-image -t hurd-raw bare-hurd.tmpl)
> >
> > it is telling me that the ’ssh’ service is not started.  Therefore,
> >
> > ssh -p 10022 root@localhost
> > ssh: connect to host localhost port 10022: Connection refused
> >
> > What do I miss?
>
> I have no idea.  This exact command works for me.  Maybe you had bad
> luck/try again?  Does `herd start ssh' work after you login as root?
>
> It could be that your "bad luck" comes from qemu networking -- maybe you
> could try running your foreign distro's qemu instead of guix's?

I do not know if it was bad luck or if "herd start ssh" does the trick
but here we go! \o/

--8<---cut here---start->8---
$ ssh -p 10022 root@localhost
The authenticity of host '[localhost]:10022 ([127.0.0.1]:10022)' can't
be established.
ECDSA key fingerprint is SHA256:iETZ8thOyFqk+35g02tRW9FRzLqilgYYlxWr/9xn/kI.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[localhost]:10022' (ECDSA) to the list of
known hosts.


  This is the GNU Hurd.  Welcome.
--8<---cut here---end--->8---

Thank you.


> > Last, I am confused:
> >
> >debian$ guix build hello --target=i586-pc-gnu hello
> >/gnu/store/09sz4qsqp3zgnbaxhzppspaxihwmfzll-hello-2.10

[..]

> It's tricky; --target is != --system: --target is a cross-build.  IOW,
> --system => (%current-system), --target => (%current-target-system).
>
> So,
>
> guix build hello --system=i586-gnu hello
>
> should give the identical hash.

What is the target?  i586-pc-gnu or i586-gnu?  The blog post mentions
'i586-pc-gnu' at the beginning and then 'i586-gnu'.  I suppose it is
'i586-gnu' since using this target produces the expected hash.
What do I miss?


All the best,
simon

Re: Reproductibility, Data Services, guix weather

[zimoun]

Hi Chris,

On Tue, 13 Oct 2020 at 21:41, Christopher Baines  wrote:

> > First, Chris could you add the fields package name and version?  Because
> > it is hard to automatically reconstruct them by parsing the output-path.
>
> Done in [1], and I've updated data.guix-patches.cbaines.net.

Neat!  I have updated my script.  Now, I need to add some build-system
support to easy the triage.  Keep you in touch.

Thank you.

> > (A working revision is 6cf35799dec60723f37d83a559429aa8b90482d5 which
> > does not seems founding in Guix repo.)
>
> So, that particular commit is just some revision of Guix with some
> patches applied. I picked it because it was the most recent
> data. There's now recent commits for the master branch itself [2] like
> [3].

Can I expect that all the revisions are there?  Or only some?


Cheers,
simon

Re: Diverse Double-Compiling, --with-c-toolchain and trusting trust

[zimoun]

Dear,

On Wed, 14 Oct 2020 at 20:12, Joshua Branson  wrote:

> This reminds me of the reflections on trusting trust:

Hehe!  The Diverse Double-Compiling (DDC) is a countermeasure against
Trusting Trust attack. :-)If you are interested by the topic, one
entry point is one of this links:

1: 

2: 

3: 

> If you get something like this working, and you'd like some help
> assembling it into a blog post, please let me know!

Thanks for the offer.  I will keep it in mind.


All the best,
simon

Re: Diverse Double-Compiling, --with-c-toolchain and trusting trust

[Joshua Branson]

Hey zimoun!

This reminds me of the reflections on trusting trust:

https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf

If you get something like this working, and you'd like some help
assembling it into a blog post, please let me know!

Thanks,

--
Joshua Branson
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
"You can have whatever you want, as long as you help enough other people get 
what they want." - Zig Ziglar

Re: [BLOG] Childhurds and GNU/Hurd substitutes

[Jan Nieuwenhuizen]

zimoun writes:

Dear Simon,

> On Thu, 08 Oct 2020 at 15:34, Jan Nieuwenhuizen  wrote:
>
>> We have just published a blog post on building your own Guix System with
>> GNU/Hurd and running it in a virtual machine; the road we traveled since
>> beginning of April and what is possible right now.  Read it here:
>>
>> https://guix.gnu.org/en/blog/2020/childhurds-and-substitutes/
>
> Amazing!

Thanks!

> On foreign distro, I have missed how to setup the “childhurd“.  The
> “guix system” is still a bit mysterious to me…

Yeah, guix system in essence "just" builds a disk-image (aka vm-image).
Then, qemu can start that image.

> Using this command line (from gnu/system/examples/bare-hurd.tmpl):
>
> guix environment --ad-hoc qemu \
>  -- qemu-system-i386 -enable-kvm -m 512  \
>   -device rtl8139,netdev=net0 -netdev 
> user,id=net0,hostfwd=tcp:127.0.0.1:10022-: \
>  -snapshot -hda \
>  $(guix system disk-image -t hurd-raw bare-hurd.tmpl)
>
> it is telling me that the ’ssh’ service is not started.  Therefore,
>
> ssh -p 10022 root@localhost
> ssh: connect to host localhost port 10022: Connection refused
>
> What do I miss?

I have no idea.  This exact command works for me.  Maybe you had bad
luck/try again?  Does `herd start ssh' work after you login as root?

It could be that your "bad luck" comes from qemu networking -- maybe you
could try running your foreign distro's qemu instead of guix's?

> Then,
>
> login> login root RET RET
> root@guixygnu ~# $(guix build hello)/bin/hello
>
> downloads, builds, and displays as expected “Hello, world!”. \o/

\o/

> Last, I am confused:
>
>debian$ guix build hello --target=586-pc-gnu hello
>/gnu/store/09sz4qsqp3zgnbaxhzppspaxihwmfzll-hello-2.10
>
>root@guixygnu ~# guix build hello
>/gnu/store/-hello-2.10
>
> What do I miss?

It's tricky; --target is != --system: --target is a cross-build.  IOW,
--system => (%current-system), --target => (%current-target-system).

So,

guix build hello --system=i586-gnu hello

should give the identical hash.

> (Sorry for these naive questions.)

You're welcome.  Thanks for looking at this!

> Thank you!  All is really neat!

Hehe, that's what we are doing it for;

Have fun!
Janneke

-- 
Jan Nieuwenhuizen  | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

Diverse Double-Compiling, --with-c-toolchain and trusting trust

[zimoun]

Hi,

Reading the recent discussions about Reproducible Builds, see [1, 2, 3],
I was in the mood to use the recent option ’–with-c-toolchain’ to
demonstrate how Guix is cool!  But I have failed because I miss some UI,
I guess.

Well, my understanding of Diverse Double-Compiling can be summarized as:

Let’s consider that you have the source code of compiler (say ’tcc’
because it compiles fast) and 2 another compilers (say ’clang’ and
’gcc’).

| step | source | compiled with | produces |
|--++---+--|
| #1   | tcc| clang | tcc-A|
| #2   | tcc| tcc-A | tcc-B|
| #3   | tcc| gcc   | tcc-C|

Nothing ensures that tcc-{A,B,C} are bit-to-bit identical –– even they
should have different binary code –– but they are functionally
equivalent, or something is already wrong.

The next steps is to recompile:

| step | source | compiled with | produces |
|--++---+--|
| #4   | tcc| tcc-B | tcc-1|
| #5   | tcc| tcc-C | tcc-2|

And now, if everything is ok, then ’tcc-1’ and ’tcc-2’ must be
bit-identical.  Otherwise, the binaries ’clang’ *or* ’gcc’ are
compromised.  Assuming that the source code of ’tcc’ is audited and not
compromised. ;-)

If the source of the compilers used at step #1 and #2 are available,
then the same procedure can be applied to detect an attack.


Well, the idea is to implement the procedure with Guix: step #1,

  guix build tcc --with-c-toolchain=tcc=clang-toolchain

but then I do not know how to use the output to complete the step #2.
Is it possible to do it at the CLI level?  Or do I have to write some
Scheme?


Thank you in advance for any tips.

All the best,
simon

1: 

2: 

3: 

Re: Outreachy Applicant: An Introduction

[Aniket Patil]

Hi Lemes,

I am also emacs user and Outreachy applicant. I would suggest you to go
through tutorial of emacs which is inbuilt and then go through this video
series.

https://www.youtube.com/playlist?list=PL9KxKa8NpFxIcNQa9js7dQQIHc81b0-Xg

I hope you find it helpful.

Aniket.

On Tue, 13 Oct 2020 at 4:38 PM, Magali Lemes 
wrote:

> Hey,
> I'm using Ubuntu 20.04.1 LTS. I must say I've never used emacs before, so
> I'll try to get the hang of it.
> Sharing my progress: I decided to package the arduino IDE, but it turned
> out
> way harder than I expected, due to its many dependencies. I ended up not
> doing it, but it was a good experience because I could learn about some
> functions in Scheme - chdir, for example -, some of the phases of
> building a package - like unpacking, configuring and building - and I could
> also interact with the community, asking for help, via IRC, which is a
> very new thing for me.
> As for today, I will continue trying to package something. I'll probably
> follow
> your previous advice and begin with a R package. It seems easier, so
> hopefully
> I'll succeed.
>
> Cheers,
> Magali.
>
> Em seg., 12 de out. de 2020 às 12:06, zimoun 
> escreveu:
>
>> Hi,
>>
>> On Mon, 12 Oct 2020 at 13:00, Magali Lemes 
>> wrote:
>>
>> > Guix was fairly easy to install, I used the shell script to do that.
>>
>> Which distribution do you use?
>>
>> > I installed emacs using Guix and it worked as expected.
>>
>> Nice!
>> Personally, I manage the Emacs packages with Guix via a manifest.scm
>> file.  And in a separate profile.  My conf [1] is far from perfect but
>> if you need inspiration. :-)
>>
>> 1: 
>>
>> > I'll begin by trying to package something. So, I'll go through the
>> links you sent
>> > and see how that goes.
>>
>> Cool!
>> Do not hesitate to ask on help-guix or #guix if you encounter issues
>> on your path.  And feel free to send your progress, success or
>> failure.
>>
>>
>> All the best,
>> simon
>>
>

GNU Guix,

[Игорь]

Hello verry cool guys, I want to know, when you make the graphical installer for GNU Guix, like cala Dear GNU Guix developer command,mares?Thank you very much for your project. E-mail: por...@ya.ru

Re: [BLOG] Childhurds and GNU/Hurd substitutes

[zimoun]

Dear,

On Thu, 08 Oct 2020 at 15:34, Jan Nieuwenhuizen  wrote:

> We have just published a blog post on building your own Guix System with
> GNU/Hurd and running it in a virtual machine; the road we traveled since
> beginning of April and what is possible right now.  Read it here:
>
> https://guix.gnu.org/en/blog/2020/childhurds-and-substitutes/

Amazing!


On foreign distro, I have missed how to setup the “childhurd“.  The
“guix system” is still a bit mysterious to me…


Using this command line (from gnu/system/examples/bare-hurd.tmpl):

guix environment --ad-hoc qemu \
 -- qemu-system-i386 -enable-kvm -m 512  \
  -device rtl8139,netdev=net0 -netdev 
user,id=net0,hostfwd=tcp:127.0.0.1:10022-: \
 -snapshot -hda \
 $(guix system disk-image -t hurd-raw bare-hurd.tmpl)

it is telling me that the ’ssh’ service is not started.  Therefore,

ssh -p 10022 root@localhost
ssh: connect to host localhost port 10022: Connection refused

What do I miss?


Then,

login> login root RET RET
root@guixygnu ~# $(guix build hello)/bin/hello

downloads, builds, and displays as expected “Hello, world!”. \o/


Last, I am confused:

   debian$ guix build hello --target=586-pc-gnu hello
   /gnu/store/09sz4qsqp3zgnbaxhzppspaxihwmfzll-hello-2.10

   root@guixygnu ~# guix build hello
   /gnu/store/-hello-2.10

What do I miss?


(Sorry for these naive questions.)


Thank you!  All is really neat!

All the best,
simon

New Russian PO file for 'guix-manual' (version 1.2.0-pre1)

[Translation Project Robot]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'guix-manual' has been submitted
by the Russian team of translators.  The file is available at:

https://translationproject.org/latest/guix-manual/ru.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

https://translationproject.org/latest/guix-manual/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

https://translationproject.org/domain/guix-manual.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

The Translation Project robot, in the
name of your translation coordinator.

Re: File search progress: database review and question on triggers

[Pierre Neidhardt]

Ludovic Courtès  writes:

>> Question: How do I hook onto =guix build=?
>
> You would need a build-completion hook in the daemon, which doesn’t
> exist (yet!).  Note also that at this level we only see derivations, not
> packages.

Hmm... Can you explain me how =guix size= works with local builds?  Does
it compute the size on demand or is it stored somewhere?

-- 
Pierre Neidhardt
https://ambrevar.xyz/


signature.asc
Description: PGP signature

Re: Outreachy Applicant: An Introduction

[Catonano]

Il giorno mer 14 ott 2020 alle ore 04:28 Magali Lemes <
magalileme...@gmail.com> ha scritto:

> Hi Aniket and Bonface,
> thank you two for the nice suggestions. That was exactly what I
> was looking to get started into emacs.
>
> Magali
>
>
I'd like to suggest also this one
https://www.pluralsight.com/courses/meet-emacs

It's not free and I understand that can be a hurdle

But a similar resource (that's not available anymore, this is a renewed
one) was very helpful for me

Hope this helps







> Em ter., 13 de out. de 2020 às 21:48, Aniket Patil <
> aniket112.pa...@gmail.com> escreveu:
>
>> Hi Lemes,
>>
>> I am also emacs user and Outreachy applicant. I would suggest you to go
>> through tutorial of emacs which is inbuilt and then go through this video
>> series.
>>
>> https://www.youtube.com/playlist?list=PL9KxKa8NpFxIcNQa9js7dQQIHc81b0-Xg
>>
>> I hope you find it helpful.
>>
>> Aniket.
>>
>> On Tue, 13 Oct 2020 at 4:38 PM, Magali Lemes 
>> wrote:
>>
>>> Hey,
>>> I'm using Ubuntu 20.04.1 LTS. I must say I've never used emacs before,
>>> so
>>> I'll try to get the hang of it.
>>> Sharing my progress: I decided to package the arduino IDE, but it turned
>>> out
>>> way harder than I expected, due to its many dependencies. I ended up not
>>> doing it, but it was a good experience because I could learn about some
>>> functions in Scheme - chdir, for example -, some of the phases of
>>> building a package - like unpacking, configuring and building - and I
>>> could
>>> also interact with the community, asking for help, via IRC, which is a
>>> very new thing for me.
>>> As for today, I will continue trying to package something. I'll probably
>>> follow
>>> your previous advice and begin with a R package. It seems easier, so
>>> hopefully
>>> I'll succeed.
>>>
>>> Cheers,
>>> Magali.
>>>
>>> Em seg., 12 de out. de 2020 às 12:06, zimoun 
>>> escreveu:
>>>
 Hi,

 On Mon, 12 Oct 2020 at 13:00, Magali Lemes 
 wrote:

 > Guix was fairly easy to install, I used the shell script to do that.

 Which distribution do you use?

 > I installed emacs using Guix and it worked as expected.

 Nice!
 Personally, I manage the Emacs packages with Guix via a manifest.scm
 file.  And in a separate profile.  My conf [1] is far from perfect but
 if you need inspiration. :-)

 1: 

 > I'll begin by trying to package something. So, I'll go through the
 links you sent
 > and see how that goes.

 Cool!
 Do not hesitate to ask on help-guix or #guix if you encounter issues
 on your path.  And feel free to send your progress, success or
 failure.


 All the best,
 simon

>>>