From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 27080@debbugs.gnu.org
Subject: bug#27080: ¨make install" fails because of missing gawk
Date: Sun, 28 May 2017 11:22:10 +0200 [thread overview]
Message-ID: <m1y3thcp4t.fsf@ddl.home> (raw)
In-Reply-To: <87shjre53a.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> You are correct, however, that building from source and running “make
> install” *will* install Guix to the specified prefix. What I’m pretty
> sure does *not* happen, though, is that this *overwrites* any files that
> Ubuntu (or any other system) uses. It is well-behaved in that it
> installs things into the expected directories under the given prefix.
It does put everything into the correct directories, but that doesn't
prevent version conflicts with my Ubuntu installation. If I remember
correctly it was the locale definitions that were not compatible.
> (With the “pre-inst-env” script it’s possible to run Guix without
> installing it, so you don’t even have to run “make install” at all if
> you just want to bootstrap Guix.)
That's a useful suggestion, thanks! All I want to do is develop my own
package definitions, and eventually contribute them to the official
distribution. All I need is a way to run Guix-from-source under my user
account.
Konrad.
next prev parent reply other threads:[~2017-05-28 9:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 7:18 bug#27080: ¨make install" fails because of missing gawk Konrad Hinsen
2017-05-26 11:10 ` Ricardo Wurmus
2017-05-26 13:53 ` Konrad Hinsen
2017-05-26 14:56 ` Ricardo Wurmus
2017-05-26 16:01 ` Konrad Hinsen
2017-05-26 16:44 ` Ricardo Wurmus
2017-05-26 18:38 ` Konrad Hinsen
2017-05-26 20:27 ` Ricardo Wurmus
2017-05-28 9:22 ` Konrad Hinsen [this message]
2017-05-28 20:24 ` Ludovic Courtès
2017-05-28 20:28 ` Ludovic Courtès
2017-05-29 14:47 ` Konrad Hinsen
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=m1y3thcp4t.fsf@ddl.home \
--to=konrad.hinsen@fastmail.net \
--cc=27080@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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.