linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso-3s7WtUTddSA@public.gmane.org>
To: Scott James Remnant <scott-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Cc: linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] configure: Disable libblkid by default
Date: Fri, 17 Jul 2009 10:36:37 -0400	[thread overview]
Message-ID: <20090717143637.GM8508@mit.edu> (raw)
In-Reply-To: <E1MRWBp-0000yN-9a-eEhpo0tUqaMrEHDPZeG1zdBPR1lH4CV8@public.gmane.org>

On Thu, Jul 16, 2009 at 07:46:13PM +0100, Scott James Remnant wrote:
> Since util-linux-ng now builds libblkid by default, e2fsprogs
> should not do so.

I'm not going to be applying these patches for quite some time.  I'd
much rather have packaging scripts that *know* they will be packaging
alongside util-linux-ng use --disable-libblkid, etc. so we don't break
things for folks who might need to build e2fsprogs for distributions
that are still using util-linux --- which at the moment still have the
vast majority of the installed base, and every so often people do
actually care about running updated filesystem utilities on an older
enterprise distribution.

The at the minimum I'll want to make sure that the debian/rules file
packaged with e2fsprogs can build both for util-linux and
util-linux-ng for similar reasons, especially since Lamont hasn't
gotten back to us about potentially getting util-linux-ng packaged for
Debian yet.

							- Ted

--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-07-17 14:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 18:46 [PATCH] configure: Disable libblkid by default Scott James Remnant
     [not found] ` <E1MRWBp-0000yN-9a-eEhpo0tUqaMrEHDPZeG1zdBPR1lH4CV8@public.gmane.org>
2009-07-17 14:36   ` Theodore Tso [this message]
     [not found]     ` <20090717143637.GM8508-3s7WtUTddSA@public.gmane.org>
2009-07-17 14:54       ` Scott James Remnant
2009-07-17 15:02         ` Theodore Tso
2009-07-17 15:14           ` Scott James Remnant
2009-07-19 11:56             ` Theodore Tso
2009-07-19 14:59               ` Scott James Remnant
2009-07-19 21:27               ` Karel Zak
     [not found]                 ` <20090719212714.GA6886-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2009-07-20 14:23                   ` Theodore Tso
2009-07-20 14:26                     ` Christoph Hellwig
     [not found]                     ` <20090720142337.GH2416-3s7WtUTddSA@public.gmane.org>
2009-07-20 14:37                       ` Scott James Remnant

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=20090717143637.GM8508@mit.edu \
    --to=tytso-3s7wtutddsa@public.gmane.org \
    --cc=linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=scott-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
    --cc=util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.
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 NNTP newsgroup(s).