From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42725) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S4tNJ-0003rd-7V for qemu-devel@nongnu.org; Tue, 06 Mar 2012 07:20:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S4tMs-00049J-Mg for qemu-devel@nongnu.org; Tue, 06 Mar 2012 07:20:16 -0500 Received: from cantor2.suse.de ([195.135.220.15]:33658 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S4tMs-00048q-Cc for qemu-devel@nongnu.org; Tue, 06 Mar 2012 07:19:50 -0500 Message-ID: <4F5600E3.9010609@suse.de> Date: Tue, 06 Mar 2012 13:19:47 +0100 From: Hannes Reinecke MIME-Version: 1.0 References: <20120213132417.GG32182@redhat.com> <4F51FD52.6080407@suse.de> <4F52066B.4040206@msgid.tls.msk.ru> <20120306100705.GB7588@redhat.com> <4F55E914.3020607@msgid.tls.msk.ru> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] QEMU desired libiscsi.so clashes with libiscsi.so from iscsi-initiator-utils List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ronnie sahlberg Cc: Mike Christie , Michael Tokarev , =?ISO-8859-1?Q?Andreas_F=E4rber?= , qemu-devel@nongnu.org On 03/06/2012 12:06 PM, ronnie sahlberg wrote: > Sorry about this. >=20 > 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. >=20 Yes. >=20 > I want to solve a problem to make it available on all platforms. > I dont like to chose a suboptimal name for this reason, but I thought > I had no choice. >=20 Fully agreed. I'm perfectly fine with libiscsi ... >=20 > I am not really excited with the concept of "obscure single use > private library polluting the namespace like this" but what are my > options ? > I can live with renaming my library if that is what it takes. >=20 IMO the only sane option here is to have a separate package, containing libiscsi _only_. It can be a sub-package of existing iscsi-related things, ie contained within the existing open-iscsi _source_ repository. But having is packaged _together_ with another rpm is really bad. Plus it makes updating a nightmare. So, Mike, what about having it as a sub-package to open-iscsi? I'm all for it, especially as some partners are already asking for it ... Cheers, Hannes --=20 Dr. Hannes Reinecke zSeries & Storage hare@suse.de +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg GF: J. Hawn, J. Guild, F. Imend=F6rffer, HRB 16746 (AG N=FCrnberg)