All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs
Date: Wed, 19 Sep 2007 20:41:20 -0500	[thread overview]
Message-ID: <46F1CFC0.3070801@redhat.com> (raw)
In-Reply-To: <20070919061404.GA1628@schatzie.adilger.int>

Andreas Dilger wrote:
> It isn't possible to build an e2fsprogs via "make rpm" on SuSE and have it
> install cleanly, because they split out some of the libraries into separate
> packages.
> 
> We've got the current patch to the .spec file, but I'm open to discussion
> if it is more desirable to change the .spec to continue to build separate
> RPMs (though that is more of a distribution hassle and might need major
> changes in the .spec file).
> 

FWIW, I also have an RFE assigned to me for RHEL/Fedora to split up our
e2fsprogs packages for libcom_err and libuuid... since many
non-filesystem things now require them.   So, this is sort of going in
the opposite direction.  :)

Any idea how many distros already split it out?

-Eric

> Index: e2fsprogs-1.40.2/e2fsprogs.spec.in
> ===================================================================
> --- e2fsprogs-1.40.2.orig/e2fsprogs.spec.in
> +++ e2fsprogs-1.40.2/e2fsprogs.spec.in
> @@ -13,6 +13,10 @@
>  Url: http://e2fsprogs.sourceforge.net/
>  Prereq: /sbin/ldconfig
>  BuildRoot: %{_tmppath}/%{name}-root
> +%if %{_vendor} == "suse"
> +Obsoletes: libcom_err < %{version}
> +Provides: libcom_err = %{version}
> +%endif
>  
>  %description
>  The e2fsprogs package contains a number of utilities for creating,
> 
> Cheers, Andreas
> --
> Andreas Dilger
> Principal Software Engineer
> Cluster File Systems, Inc.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-09-20  1:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19  6:14 [PATCH] obsolete libcom-err for SuSE e2fsprogs Andreas Dilger
2007-09-20  1:41 ` Eric Sandeen [this message]
2007-09-20  5:09   ` Andreas Dilger
2007-09-20 20:22     ` Eric Sandeen
2007-09-20 20:42       ` Andreas Dilger
2007-09-20 21:54       ` Theodore Tso
2007-09-24  9:25         ` Karel Zak
     [not found]           ` <20070924092539.GC2819-CxBs/XhZ2BtHjqfyn1fVYA@public.gmane.org>
2007-09-24 12:40             ` Theodore Tso
     [not found]               ` <20070924124035.GA4209-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2007-09-24 13:16                 ` Eric Sandeen
2007-09-24 13:16                   ` Eric Sandeen
2007-09-25  9:14                 ` Karel Zak
2007-09-25 10:11                   ` Kay Sievers
2007-09-25 12:34                     ` Karel Zak
2007-09-25 15:20                       ` Theodore Tso
     [not found]                       ` <20070925123454.GE2806-CxBs/XhZ2BtHjqfyn1fVYA@public.gmane.org>
2007-09-25 20:25                         ` Kay Sievers
2007-09-25 20:57                           ` Karel Zak
2007-09-25 21:35                           ` Christoph Hellwig
2007-09-25  9:27       ` Matthias Koenig

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=46F1CFC0.3070801@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.