From: Ricardo Wurmus <rekado@elephly.net>
To: Doron Behar <doron.behar@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Trying to contribute packages: ./pre-inst-env doesn't work
Date: Wed, 15 May 2019 23:26:08 +0200 [thread overview]
Message-ID: <87bm039zpr.fsf@elephly.net> (raw)
In-Reply-To: <20190515094629.hcxxxddpgoirwhza@NUC.doronbehar.com>
Doron Behar <doron.behar@gmail.com> writes:
> Plus, do I have to run make after every change to a package definition!?
> Will it compile everything from the ground up after every such change? I
> wish these technical details would have been documented...
“make” does not cause recompilation of unchanged things. This is
not particular to Guix, so it’s not documented as part of Guix.
> I also noticed it runs GUILEC - is it really necessary?
It compiles Guile modules. Using compiled modules is faster than having
to interpret everything. You can try without compiling changed modules
but the performance penalty when you have lots of interpreted modules
will likely be hard to tolerate.
> It seems that we, package maintainers, or to put it simply - the
> community, need to be too much involved in the source code of
> everything in order to help the distributions.
Packages in Guix are Scheme values bound to variable names. Packaging
is a simple form of programming.
> because as I dive more and more into
> Guix I feel there have been made a lot of poor design choices in it..
This is a surprising statement and naturally I disagree with it :) I
suggest to take a step back when the frustration of learning something
new makes you want to say harsh things.
--
Ricardo
next prev parent reply other threads:[~2019-05-15 21:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 8:06 Trying to contribute packages: ./pre-inst-env doesn't work Doron Behar
2019-05-15 8:46 ` Gábor Boskovits
2019-05-15 9:46 ` Doron Behar
2019-05-15 10:22 ` Doron Behar
2019-05-15 10:46 ` Gábor Boskovits
2019-05-15 14:49 ` Doron Behar
2019-05-15 15:04 ` Ricardo Wurmus
2019-05-15 16:10 ` Doron Behar
2019-05-15 10:41 ` Gábor Boskovits
2019-05-15 14:31 ` Doron Behar
2019-05-15 16:33 ` Amirouche
2019-05-15 16:37 ` Amirouche
2019-05-15 21:26 ` Ricardo Wurmus [this message]
2019-05-16 9:30 ` Doron Behar
2019-05-15 9:08 ` pelzflorian (Florian Pelz)
2019-05-15 10:06 ` Doron Behar
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=87bm039zpr.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=doron.behar@gmail.com \
--cc=help-guix@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.
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).