From: Mark H Weaver <mhw@netris.org>
To: Ignacio Torres Masdeu <i@itorres.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Fix artanis paths
Date: Tue, 09 Aug 2016 23:42:37 -0400 [thread overview]
Message-ID: <87ziolxpaq.fsf@netris.org> (raw)
In-Reply-To: <86eg5yg62o.fsf@itorres.net> (Ignacio Torres Masdeu's message of "Tue, 09 Aug 2016 02:05:19 +0200")
Ignacio Torres Masdeu <i@itorres.net> writes:
> The last patch[1] for artanis added the DESTDIR path to place files in
> $DESTDIR/etc.
>
> [1] http://lists.gnu.org/archive/html/guix-devel/2016-03/msg00813.html
>
> This didn't account for the fact that $DESTDIR is used in the build
> system install process as a prefix for other files and the effect was
> that those files were effectively copied in $out/$out/{bin/share}:
In general, we should be setting PREFIX to $out (i.e. /gnu/store/...),
and leaving DESTDIR unset. Conventionally, these two variables have
different meanings: PREFIX is where the files are expected to be when
the code is run. DESTDIR is meant as a temporary staging area when
building a package, with the expectation that it will be packed up into
a binary package and later extracted into PREFIX. So, with this in
mind:
> + (list (string-append "MOD_PATH=" mod_dir)
> + (string-append "MOD_COMPILED_PATH=" mod_dir)
> + "PREFIX="
> (string-append "DESTDIR=" out)))
I think that this should be (string-append "PREFIX=" out) and DESTDIR
should be left unset.
I haven't looked at the details of this package, or tried to build it,
but I'd like to see a solution that follows the conventions above, if
possible. Would you be willing to try this?
Thanks for your efforts!
Mark
next prev parent reply other threads:[~2016-08-10 3:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 0:05 [PATCH] Fix artanis paths Ignacio Torres Masdeu
2016-08-10 3:42 ` Mark H Weaver [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-03 2:08 Adonay Felipe Nogueira
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=87ziolxpaq.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=i@itorres.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 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).