From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>, mitchb@mit.edu
Subject: Re: [PATCH] e2fsprogs: create com_err.h symlink in includedir
Date: Sun, 20 Feb 2011 18:10:15 -0500 [thread overview]
Message-ID: <20110220231015.GA4001@thunk.org> (raw)
In-Reply-To: <4D5C1103.8060403@redhat.com>
On Wed, Feb 16, 2011 at 12:01:39PM -0600, Eric Sandeen wrote:
> After debian bug #192277, debian/rules started making a symlink
> to com_err.h in /usr/include. Now I have Fedora bug #550889
> for the same issue, and perhaps it's time to make this symlink
> by default, rather than fixing it up in packaging steps?
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Pulled into the e2fsprogs tree, with the following change:
[ Changed by tytso to remove the explicit -s option; this will
default to creating a hard link by default, which slightly faster.
If people want to use symlinks for all links during the install
process, they can use configure option --enable-symlink-install.
The reason for this change is that some file systems, like AFS,
don't support symlinks, and AFS users complain when they can't build
or install into AFS. So I don't want to use symlinks
unconditionally without a way of switching things back and forth,
and it's easier if we just make all links made during the install
process to be hard links or sym links. ]
- Ted
next prev parent reply other threads:[~2011-02-20 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 18:01 [PATCH] e2fsprogs: create com_err.h symlink in includedir Eric Sandeen
2011-02-20 23:10 ` Ted Ts'o [this message]
2011-03-19 15:03 ` Eric Sandeen
2011-06-16 20:39 ` Eric Sandeen
2011-06-17 2:31 ` Ted Ts'o
2011-06-17 3:54 ` Andreas Dilger
2011-06-17 14:27 ` Eric Sandeen
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=20110220231015.GA4001@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=mitchb@mit.edu \
--cc=sandeen@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 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.