qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, "Hannes Reinecke" <hare@suse.de>,
	"ronnie sahlberg" <ronniesahlberg@gmail.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] QEMU desired libiscsi.so clashes with libiscsi.so from iscsi-initiator-utils
Date: Tue, 06 Mar 2012 18:10:38 +0400	[thread overview]
Message-ID: <4F561ADE.2040301@msgid.tls.msk.ru> (raw)
In-Reply-To: <20120306111526.GG7588@redhat.com>

06.03.2012 15:15, Daniel P. Berrange wrote:
> On Tue, Mar 06, 2012 at 10:06:38PM +1100, ronnie sahlberg wrote:
>> Sorry about this.
>>
>> First, libiscsi is a really good name for a general purpose
>> multiplatform library, like libiscsi.
>> Second,  a generic name like this is a horribly poor idea for a single
>> distribution/ single use / obscure private library.
>
> Yes, I agree it was a bad idea for the Fedora/RHEL admin to have done
> this for iscsi-initiator-utils packaging. Now this exists though, the
> library name&  ABI has to be maintained in RHEL for back-compatibility,
> so sadly we can't easily fix this. At the same time I really want to
> include your iSCSI support in Fedora/RHEL.

Which ABI you're talking about?  The library is _internal_ to the package,
there should be no users of it outside of this single set of utilities.
Can you be a bit more specific please?

> So, IMHO, the simplest approach is to just avoid the namespace clash
> by calling your library  libiscsiclient

Thanks,

/mjt

  reply	other threads:[~2012-03-06 14:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 13:24 [Qemu-devel] QEMU desired libiscsi.so clashes with libiscsi.so from iscsi-initiator-utils Daniel P. Berrange
2012-03-03  6:43 ` ronnie sahlberg
2012-03-03 11:15   ` Andreas Färber
2012-03-03 11:54     ` Michael Tokarev
2012-03-06 10:07       ` Daniel P. Berrange
2012-03-06 10:38         ` Michael Tokarev
2012-03-06 11:06           ` ronnie sahlberg
2012-03-06 11:15             ` Daniel P. Berrange
2012-03-06 14:10               ` Michael Tokarev [this message]
2012-03-06 12:19             ` Hannes Reinecke
2012-03-06 19:58               ` Mike Christie
2012-03-06 20:13                 ` Mike Christie
2012-03-07  1:51                   ` ronnie sahlberg
2012-03-07  2:30                     ` Mike Christie
2012-03-06 10:02   ` Daniel P. Berrange

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=4F561ADE.2040301@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=afaerber@suse.de \
    --cc=berrange@redhat.com \
    --cc=hare@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.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 NNTP newsgroup(s).