From: Lakshmi Prasannakumar <lakshmiprasannakumaran@gmail.com>
To: boskovits@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: Video Documentation for GNU GUIX (an Outreachy project)
Date: Thu, 18 Oct 2018 14:52:30 +0530 [thread overview]
Message-ID: <CA+H0LROyOtdB-ZgtB_wkhkr1mTpQ3R4ANtDDY9veZ-Gi0xiT4g@mail.gmail.com> (raw)
In-Reply-To: <CAE4v=phvW_tNqOjbA82mA5kpdxBqmAtjHudQuoK-c_jnidK8Rg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3382 bytes --]
Hi Gábor,
I have followed the Binary-Installation procedures and installed the hello
package to my root.
The next step I understand is to add another package from the list in
https://www.gnu.org/software/guix/packages/
I tried following this step to install a package from the list i.e. 4ti2
1.6.7 using the below commands:
*guix package -i 4ti2 1.6.7*
However, I got the error as :
*guile: warning: failed to install localehint: Consider installing the
`glibc-utf8-locales' or `glibc-locales' package anddefining `GUIX_LOCPATH',
along these lines: guix package -i glibc-utf8-locales export
GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"See the "Application Setup"
section in the manual, for more info.*
Is it due my incomplete GUIX installation or are there further steps to
follow?
Thanks,
Lakshmi Prasannakumar
Bangalore
On Wed, Oct 17, 2018 at 1:41 PM Gábor Boskovits <boskovits@gmail.com> wrote:
> Hello Lakshmi,
> Welcome to Guix!
>
> Björn Höfling <bjoern.hoefling@bjoernhoefling.de> ezt írta (időpont:
> 2018. okt. 17., Sze 8:45):
>
>> Hi Lakshmi,
>>
>> On Wed, 17 Oct 2018 09:04:40 +0530
>> Lakshmi Prasannakumar <lakshmiprasannakumaran@gmail.com> wrote:
>>
>> > Hi Björn,
>> > I write to you in regards to the project description seen at the
>> > Outreachy project list. I would like to join your community and start
>> > contributing to the documentation part of it.
>>
>> Welcome to Guix! I'm adding the public mailing list on CC, so other
>> community members can also answer if necessary. Also adding Gabor on
>> CC, who is the main mentor.
>>
>> > Though I have joined
>> > the IRC channel for GNU GUIX, I'm continually receiving the error
>> > message as below on sending messages:
>> > == Cannot send to nick/channel
>>
>> There was recently a spam attack on the freenode IRC network. Since
>> then you need to register your nick name before it is possible to join
>> the #guix channel. If you haven't done that yet, here are the
>> instructions:
>>
>> https://freenode.net/kb/answer/registration
>>
>> You can also join the mailing list and write there.
>>
>> > My understanding regarding the project contribution is to make
>> > video tutorials on how to install and use GNU GUIX.
>> > Could you kindly direct me with some initial task so that I can start
>> > working on it and get familiar with the environment?
>>
>> Yes, that's right, video documentation is the job. One requirement for
>> Outreachy is to make a first, formal contribution to the project. For
>> Guix that means you could add a new package.
>>
>> But the very first step is to install Guix and get used to it. You can
>> install Guix either on top of another Linux-Distribution or standalone,
>> in a virtual mashine or on real hardware. On top of an existing distro
>> is probably the easiest step.
>>
>> The docs for installation should be linked from the Outreachy Project
>> site, I post it also here:
>>
>>
>> https://www.gnu.org/software/guix/manual/en/html_node/Binary-Installation.html#Binary-Installation
>
>
> Yes, installation would be the first step.
>
>
>>
>> If you have any questions feel free to ask (preferably on the mailing
>> list, or if it works for you, on IRC).
>>
>> Yours,
>>
>> Björn
>>
>
> Best regards,
> g_bor
>
>>
[-- Attachment #2: Type: text/html, Size: 7417 bytes --]
next prev parent reply other threads:[~2018-10-18 9:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+H0LRPUfE=LmSETuasan3bEjEkGPXRFoE5Qrd-9G8DYO8buTQ@mail.gmail.com>
2018-10-17 6:45 ` Video Documentation for GNU GUIX (an Outreachy project) Björn Höfling
2018-10-17 8:11 ` Gábor Boskovits
2018-10-18 9:22 ` Lakshmi Prasannakumar [this message]
2018-10-18 11:46 ` Björn Höfling
2018-10-18 11:52 ` Gábor Boskovits
2018-10-18 12:37 ` Lakshmi Prasannakumar
2018-10-18 13:00 ` Gábor Boskovits
2018-10-23 12:34 ` Lakshmi Prasannakumar
2018-10-23 18:22 ` Gábor Boskovits
2018-10-29 9:25 ` Gábor Boskovits
2018-10-29 18:12 ` Lakshmi Prasannakumar
2018-10-29 19:57 ` Björn Höfling
2018-10-29 20:18 ` Lakshmi Prasannakumar
2018-10-29 20:27 ` Björn Höfling
2018-10-29 20:40 ` Lakshmi Prasannakumar
2018-10-29 20:58 ` Gábor Boskovits
2018-10-30 18:20 ` Lakshmi Prasannakumar
2018-10-31 4:45 ` Lakshmi Prasannakumar
2018-10-31 4:46 ` Lakshmi Prasannakumar
2018-10-31 7:18 ` Gábor Boskovits
2018-10-31 7:20 ` Gábor Boskovits
2018-10-31 8:32 ` Gábor Boskovits
2018-11-01 17:01 ` Lakshmi Prasannakumar
2018-11-01 17:36 ` Gábor Boskovits
2018-11-01 17:48 ` Lakshmi Prasannakumar
2018-10-29 20:03 ` Lakshmi Prasannakumar
2018-10-29 20:25 ` Björn Höfling
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+H0LROyOtdB-ZgtB_wkhkr1mTpQ3R4ANtDDY9veZ-Gi0xiT4g@mail.gmail.com \
--to=lakshmiprasannakumaran@gmail.com \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).