From: Ulrich Drepper <drepper@gmail.com>
To: Andreas Schwab <schwab@redhat.com>
Cc: libc-hacker@sourceware.org
Subject: Re: [PATCH] Define vardbdir relative to prefix
Date: Fri, 01 Jul 2011 23:29:00 -0000 [thread overview]
Message-ID: <CAOPLpQeLVVn6XT+sOjbR0xzB-4am9FNv7GkHvu-PyNcRCe4Ksg@mail.gmail.com> (raw)
In-Reply-To: <m3y60ie0z8.fsf@redhat.com>
On Fri, Jul 1, 2011 at 06:42, Andreas Schwab <schwab@redhat.com> wrote:
> +# Where to install data files which the programs modify
> +# while they run, and that pertain to one specific machine.
> +ifndef localstatedir
> +localstatedir = $(prefix)/var
> +endif
> +inst_localstatedir = $(install_root)$(localstatedir)
> +
> # Directory for the database files and Makefile for nss_db.
> ifndef vardbdir
> -vardbdir = /var/db
> +vardbdir = $(localstatedir)/db
This doesn't work because the db files are always searched for in
/var/db. This is why the Makefiles are as they are now.
What is the reason for this proposed change?
prev parent reply other threads:[~2011-07-01 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 10:42 Andreas Schwab
2011-07-01 23:29 ` Ulrich Drepper [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=CAOPLpQeLVVn6XT+sOjbR0xzB-4am9FNv7GkHvu-PyNcRCe4Ksg@mail.gmail.com \
--to=drepper@gmail.com \
--cc=libc-hacker@sourceware.org \
--cc=schwab@redhat.com \
/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).