<html style="direction: ltr;">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body style="direction: ltr;" bidimailui-charset-is-forced="true"
smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<div id="smartTemplate4-template"> </div>
<br>
<div id="smartTemplate4-quoteHeader">
<style type="text/css">
blockquote [[ /*Fri, 13 Feb 2015 14:11:49 +0100*/ color: navy !important; background-color: RGB(245,245,245) !important; padding: 0 15 10 15 !important; margin: 15 0 0 0; border-left: #1010ff 2px solid;]]
blockquote blockquote {{ /*Fri, 13 Feb 2015 14:11:49 +0100*/ color: maroon !important; background-color: RGB(235,235,235) !important; border-left-color:maroon !important}}
blockquote blockquote blockquote {{ /*Fri, 13 Feb 2015 14:11:49 +0100*/ color: green !important; background-color: RGB(225,225,225) !important; border-left-color:teal !important}}
blockquote blockquote blockquote blockquote {{ /*Fri, 13 Feb 2015 14:11:49 +0100*/ color: purple !important; background-color: RGB(215,215,215) !important; border-left-color: purple !important}}
blockquote blockquote blockquote blockquote blockquote {{ /*Fri, 13 Feb 2015 14:11:49 +0100*/ color: teal !important; background-color: RGB(205,205,205) !important; border-left-color: green !important}}
</style><i><b>Nikos Mavrogiannopoulos <a class="moz-txt-link-rfc2396E" href="mailto:nmav@redhat.com"><nmav@redhat.com></a></b></i>
wrote on Fri, 13 Feb 2015 14:11:49 +0100:</div>
<blockquote cite="mid:1423833109.2423.32.camel@redhat.com"
type="cite">
<pre wrap="">On Fri, 2015-02-13 at 15:21 +0330, Hedayat Vatankhah wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear all,
I don't know if this has been discussed before, but I didn't find any.
Summary: I have a proposal to make it easier for maintainers to have
multiple versions of the same library in distro (by making it
*naturally* possible) (and with minimal maintenance overhead), and for
users/developers to get their desired version(s) installed. Proposal
in brief: instead of packaging libfoo as libfoo, the maintainer *can*
package it as libfooVER (e.g. libfoo2) and create libfoo/libfoo-devel
package which depends on libfoo2/libfoo2-devel. Now, libfoo-3 package
can be packaged as libfoo3, and both can be installed simultaneously
(assuming that they provide different .so versions, otherwise it could
be provided as an update to libfoo2). Notice that once libfoo2 is in
the repos, newer versions (libfoo3/libfoo4) should not require a
package review.
</pre>
</blockquote>
<pre wrap="">
I'm not against it, for the libraries which provide proper symbol
versioning. Otherwise, if you only rely on the soname, you may end up in
a situation where a program crashes because of inter-dependencies which
make it link with both libfoo1 and libfoo2 which provide the same (but
most likely incompatible) symbols.
</pre>
</blockquote>
I wonder if it should be taken care of by packages, rather than
libraries themselves. I'm not sure, but probably most of the
libraries doesn't have such symbol versioning in place. <br>
Also, note that all packages must be linked to the 'default'
version, unless strictly needed. And probably linking to libfoo1 and
libfoo2 simultaneously should be checked automatically (e.g. AutoQA)
and forbidden completely. <br>
<br>
Thanks,<br>
Hedayat<br>
</body>
</html>