From: Dan Partelly <dan_partelly@rdsor.ro>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Suboptimal experience
Date: Mon, 18 Jun 2018 21:08:27 +0300 [thread overview]
Message-ID: <A35F655B-D1DF-4574-9205-3F41FF7086CD@rdsor.ro> (raw)
In-Reply-To: <d26208b96c61eb788214074d106bdf4d@lepiller.eu>
>
> Thank you for your advice :) I think you're right: we are still beta, so
> errors are to be expected from time to time. We should fix them before we
> go 1.0. That said, the system is robust enough that you can always recover
> from said errors.
>
Good. Now, give current state of affairs combined with my lack of experience with the system I wont install it for work anywhere as some fo you guys do, but I will install it on an old laptop and I will try to build my Linux recovery images with it. This will give me time to learn it and Ill take it from here. The truth is that despite the negatives of the first encounter the system has some characteristics that are too good to pass. And you where right when you told me that is very easy to extend and “make it your own”.
Which is the right mailing list for asking question regarding packaging software, hooking into build system and so on (ofc, packaging discussion in the limit of your core values ) ?
With thanks
next prev parent reply other threads:[~2018-06-18 18:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 10:09 Suboptimal experience Dan Partelly
2018-06-17 15:40 ` Julien Lepiller
2018-06-17 19:55 ` Dan Partelly
2018-06-17 20:09 ` Julien Lepiller
2018-06-17 20:13 ` Dan Partelly
2018-06-17 20:16 ` Julien Lepiller
2018-06-17 17:31 ` Mark H Weaver
2018-06-17 19:51 ` Dan Partelly
2018-06-18 11:11 ` swedebugia
2018-06-18 15:01 ` Dan Partelly
2018-06-18 15:52 ` Julien Lepiller
2018-06-18 18:08 ` Dan Partelly [this message]
2018-06-18 18:29 ` Nils Gillmann
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=A35F655B-D1DF-4574-9205-3F41FF7086CD@rdsor.ro \
--to=dan_partelly@rdsor.ro \
--cc=guix-devel@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 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).