Severity: normal
Brandon wrotes:
You might want to consider only offering a dev version of guichan, and
require that packages using guichan link statically. This is
recommended by the debian policy manual in certain cases, such as for
"libraries whose interfaces are in flux or under development."
http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-static
Guichan upstream recommends that every project that uses guichan
includes the source files manually in their project. I think the end
effect is the same thing as linking statically. Although with this
solution, there would be no libguichan* or libguichan-dev package.
http://guichan.sourceforge.net/wiki/index.php/Getting_started
-Brandon
Hello,
bumping SONAMES is a good thing for often needed packages and if
upstream provides SONAME support, I will include it.
The current solution (with conflicts) is okay. So I set the severity of
this bug to 'normal' and I will close it if upstream (and after that
this package) provides the support.
--
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
E-Mail: [EMAIL PROTECTED]
Homepage: http://www.Linux-Dev.org/
begin:vcard
fn;quoted-printable:Patrick Matth=C3=A4i
n;quoted-printable:Matth=C3=A4i;Patrick
org:Ameus IT-Systeme;Technik
adr:;;Technologiepark 21;Paderborn;Nordrhein-Westfalen;33100;Deutschland
email;internet:[EMAIL PROTECTED]
x-mozilla-html:TRUE
url:http://www.ameus.de/
version:2.1
end:vcard
