From: Fredrik Salomonsson <plattfot@posteo.net>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: setup c/c++ development environment
Date: Sun, 14 Mar 2021 19:25:46 -0700 [thread overview]
Message-ID: <87eeghqhjp.fsf@posteo.net> (raw)
In-Reply-To: <K9-EPaUcyvWsZAL_GDmk34t6u00WSaEod-_pD_bU1mDzkRRYjxdfCPrIC7Wq6VBiEOGBjnMJaGRPEKR81T_ae_J95IsHY4tHWFc_tiA-lfY=@elenq.tech>
Ekaitz Zarraga <ekaitz@elenq.tech> writes:
> So the workflow with guix build is not very good for development but
> for CI and stuff like that because you are going to rebuild everything.
That pretty much sums it up.
> Thanks for the explanations.
No problem.
--
s/Fred[re]+i[ck]+/Fredrik/g
next prev parent reply other threads:[~2021-03-15 2:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <GZyuhieLJ3BWP4kae37ZbozD8mpuvUi1Wc2M9bXr9QDDgL6nUQDmi0Nye0j4fSxLn1nGjc3Ply6KPTgSq1aEiop43LAGebaTf7XJQyuekeg=@elenq.tech>
2021-03-11 20:03 ` setup c/c++ development environment Fredrik Salomonsson
2021-03-13 19:29 ` Ekaitz Zarraga
2021-03-15 2:25 ` Fredrik Salomonsson [this message]
2021-03-04 16:22 Roy Lemmon
2021-03-04 19:02 ` Fredrik Salomonsson
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=87eeghqhjp.fsf@posteo.net \
--to=plattfot@posteo.net \
--cc=ekaitz@elenq.tech \
--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).