From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>,
Andrew Burgess <andrew.burgess@embecosm.com>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] configure: Use $prefix for emacs, even when pkg-config is available.
Date: Sat, 28 Nov 2015 17:02:50 +0200 [thread overview]
Message-ID: <m2k2p2rwth.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87egfa2rye.fsf@zancas.localnet>
On Sat, Nov 28 2015, David Bremner <david@tethera.net> wrote:
> Andrew Burgess <andrew.burgess@embecosm.com> writes:
>
>> Assumming that you have pkg-config installed, emacs installed, and the
>> command 'pkg-config emacs --variable sitepkglispdir' returns a
>> directory that only root can write to, then the make install above
>> should fail.
>
> I agree that the current behaviour is probably wrong. I'm not sure if we
> need more control here as Tomi suggests. My biggest concern is that
> emacs.pc seems to be rather specific to fedora / redhat packaging, which
> makes it hard for me to evaluate both the current handling and this
> patch. Do any any Fedora users have opinions on just dropping the
> handling of "pkg-config emacs"? Or am I missing other places that
> pkg-config file is available?
Now that I looked this a bit more I tend to agree with David:
default PREFIX is /usr/local
and $ pkg-config emacs --variable sitepkglispdir
outputs
/usr/share/emacs/site-lisp
(in default case we should mangle /local/ there in between ... :/ ).
package managers can add
./configure ---emacslispdir=`pkg-config emacs --variable sitepkglispdir`
in their build scripts.
>
> d
Tomi
next prev parent reply other threads:[~2015-11-28 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 17:32 [PATCH] configure: Use $prefix for emacs, even when pkg-config is available Andrew Burgess
2015-11-26 18:45 ` Tomi Ollila
2015-11-28 13:07 ` David Bremner
2015-11-28 15:02 ` Tomi Ollila [this message]
2015-12-06 16:04 ` [PATCH] configure: drop use of "pkg-config emacs" David Bremner
2015-12-06 16:10 ` David Bremner
2015-12-06 18:10 ` Tomi Ollila
2015-12-10 1:07 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2k2p2rwth.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=andrew.burgess@embecosm.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.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 public inbox
https://yhetil.org/notmuch.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).