all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: oury.dustin@posteo.net
To: Julien Lepiller <julien@lepiller.eu>
Cc: Help guix <help-guix@gnu.org>
Subject: Re: Maybe I made a mistake?
Date: Sun, 09 Jun 2019 23:38:20 +0200	[thread overview]
Message-ID: <ab388545c37b1d5d72ca0269162f8e8e@posteo.net> (raw)
In-Reply-To: <965510AC-46B2-42A3-94A1-291F33D02385@lepiller.eu>

I'm aware that binaries packaged for Debian and derivatives like Ubuntu 
don't work. However, not being a coder or good with reading or writing 
scheme code, I'm having to work around a few of these issues.

Regarding documentation, I feel as if the manual expects a certain 
familiarity with writing scheme code, and there isn't a lot of 
documentation for diagnosing little problems like there is with Debian 
and Ubuntu. I guess that comes down to how widespread those distros are 
in the GNU/Linux community.

On 08.06.2019 10:12, Julien Lepiller wrote:
> Le 8 juin 2019 09:18:39 GMT+02:00, Ricardo Wurmus <rekado@elephly.net> 
> a écrit :
>> 
>> Hi,
>> 
>>> Some simple
>>> packaged software that work on those distros  like Debian don't work
>>> with Guix System […]
>> 
>> Do you mean binaries that were packaged for Debian won’t work 
>> unchanged
>> on Guix System?  This is expected as Guix does not provide libraries
>> and
>> the loader at the location where a Debian binary would expect them.
>> 
>> You would need to package the software for Guix to use it there.
> 
> Packaging software is not as hard as you think it is, but if you lack
> the time to learn, you can still add your sohtware to that list:
> https://libreplanet.org/wiki/Group:Guix/Wishlist
> 
> It's not guaranteed that someone will work on it, as we are all 
> volunteers.
> 
>> 
>>> and I also find the documentation to be really hard
>>> for the non-tech savvy like me to understand. I'm confused when I
>>> should mess with my configuration file or when to do things manually,
>>> like adding a supplementary group for my primary account.
>> 
>> All of this should be done via the configuration file as the system is
>> mostly stateless, i.e. when you reboot your system is essentially set
>> up
>> from scratch using the files that were generated when you last ran
>> “guix
>> system reconfigure”.
>> 
>>> I really want to like Guix, but for now I might have to switch to
>>> something easier until the documentation gets fleshed out and more
>>> packages that aren't in yet are added to avoid frustration.
>> 
>> Can you point to specific problems you have with the documentation?
>> 
>> --
>> Ricardo

      reply	other threads:[~2019-06-09 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-08  2:38 Maybe I made a mistake? oury.dustin
2019-06-08  7:18 ` Ricardo Wurmus
2019-06-08  8:12   ` Julien Lepiller
2019-06-09 21:38     ` oury.dustin [this message]

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=ab388545c37b1d5d72ca0269162f8e8e@posteo.net \
    --to=oury.dustin@posteo.net \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    /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.