all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ben Sturmfels <ben@sturm.com.au>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Overriding PostGIS install directories
Date: Wed, 24 Jan 2018 15:28:54 +0100	[thread overview]
Message-ID: <87wp07z5y1.fsf@gnu.org> (raw)
In-Reply-To: <87po65nzdi.fsf@sturm.com.au> (Ben Sturmfels's message of "Sat, 20 Jan 2018 11:32:41 +1100")

Hi,

Ben Sturmfels <ben@sturm.com.au> skribis:

> On Fri, 19 Jan 2018, Ludovic Courtès wrote:
>
>> However, I’d recommend simply patching ‘configure’ itself in a snippet,
>> using ‘substitute*’.  That way, you won’t have to add these dependencies
>> and extra phase.
>
> Thanks, substitute* is much neater and changing configure directly is
> working.
>
> I've just discovered though that the build includes makefile templates
> from the input postgres package, eg
> ...-postgresql-10.1/lib/pgxs/src/makefiles/pgxs.mk and parents. These
> makefiles are created from a separate run of `pg_config --sharedir` when
> building postgresql.
>
> I wonder whether it would be simpler to mock the "pg_config" program to
> return the paths I want, rather than patch out all the calls to it. Is
> that possible to do for a package and its inputs? What do you think?

I guess it all depends on the number of ‘pg_config’ invocations that
need to be patch, and whether each one needs different treatment.  We
should minimize complexity.

Ludo’.

      reply	other threads:[~2018-01-24 14:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19  5:10 Overriding PostGIS install directories Ben Sturmfels
2018-01-19 13:27 ` Ludovic Courtès
2018-01-20  0:32   ` Ben Sturmfels
2018-01-24 14:28     ` Ludovic Courtès [this message]

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=87wp07z5y1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=ben@sturm.com.au \
    --cc=guix-devel@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.
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.