From: zimoun <zimon.toutoune@gmail.com>
To: Lulu <me@erkin.party>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Hello from new Outreachy applicant
Date: Fri, 9 Oct 2020 10:01:10 +0200 [thread overview]
Message-ID: <CAJ3okZ1Uh5O3H1eBFu7kbfbFuDe-+TiaOhTiYohKfo0YJOak_A@mail.gmail.com> (raw)
In-Reply-To: <1767246561.13337.1602214800667@office.mailbox.org>
Dear,
On Fri, 9 Oct 2020 at 05:40, Lulu <me@erkin.party> wrote:
> > Have you already tried GNU Guix? The package manager on foreign
> > distro? The full Guix System?
> > If yes, are you comfortable with? Feedback is very welcome. :-)
>
> I tried Guix on a foreign distro but ran into some problems with
> SELinux and locales. Do you recommend using GuixSD on a virtual
> machine, or do you think a foreign installation would be easier for
> development? I reckon a setup for internal development wouldn't be
> the same as a setup for the end-user. I think I might need to work
> directly from the trunk, so maybe I need to get familiar with
> `guix environment' for testing? I'd appreciate some tips on this.
I am using the Guix package manager on the top of Debian; installed
via the Binary Install. Let's refer to Guix as the package manager.
:-) The nice point with Guix is the flexibility and hackability for
the end-user. Once you are familiar with [1], the next natural step
is:
git clone https://git.savannah.gnu.org/git/guix.git
cd guix
guix environment guix --pure
./bootstrap
./configure --localstatedir=/var/
make -j 4 # whatever number fits your machine
Then you have a fresh compiled Guix that you can run with:
./pre-inst-env guix help
But don't cut the corners. The first step is to have a working Guix.
Which distro do you use? About the locales, if you start a thread on
help-guix@gnu.org describing your problem, then the setup will be
fine. :-)
About SELinux, I do not know... I do the job on the foreign distro
side. You could ask about specific issue on 'help-guix' or folks on
#guix will advice you.
[1] https://guix.gnu.org/manual/devel/en/guix.html#Getting-Started
> > Well, last but not least, what topic you may be interested in to work on?
>
> I decided on the task to add a `guix git log' subcommand, out of the
> two tasks on the Outreachy page. :-) [1]
>
> Aside from that, can you tell me more about how this mentorship
> process works? Is there a regular schedule with meetings or progress
> reports or such?
Nice!
Basically, the key to success is communication. Raise the hand _as
soon as possible_.
Then my advice is: everyday log what you are doing. It may be only
one or two lines, sometimes more. Once a week (at least), collect the
items and send me (privately) maybe with some patches or a branch to
pull for testing. The idea is to know your progress and your blocking
points and then help you. On a weekly or bi-weekly basis, voice (or
video) chat with any mean which suits you (especially your timezone).
> [1]: https://www.outreachy.org/outreachy-december-2020-internship-round/communities/gnu-guix/#add-a-subcommand-showing-gnu-guix-history-of-all-p
All the best,
simon
next prev parent reply other threads:[~2020-10-09 8:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 17:16 Hello from new Outreachy applicant Lulu
2020-10-07 21:51 ` Brett Gilio
2020-10-08 15:04 ` Lulu
2020-10-08 21:40 ` zimoun
2020-10-09 3:40 ` Lulu
2020-10-09 8:00 ` Gábor Boskovits
2020-10-09 8:18 ` zimoun
2020-10-09 8:01 ` zimoun [this message]
2020-10-12 12:11 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ1Uh5O3H1eBFu7kbfbFuDe-+TiaOhTiYohKfo0YJOak_A@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=me@erkin.party \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.