Debian Developers - libxslt1 / libxslt1.1 clean-up, comments welcome

This is Interesting: Free IT Magazines  
Home > Archive > Debian Developers > August 2005 > libxslt1 / libxslt1.1 clean-up, comments welcome





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author libxslt1 / libxslt1.1 clean-up, comments welcome
Mike Hommey

2005-08-11, 5:55 pm

Hello,

I'm about to remove the libxslt1 package, which has been created a long
time ago for backward compatibility, when upstream did screw up ABI and
removed support for the libxsltbreakpoint library.

Now that no package depend on it, I am going to remove it, but that
leaves a libxslt1.1 package alone, not really respectful of the debian
standards for package naming.

I was wondering if I should come back to good practice and provide a
libxslt1 package with the library, and a dummy libxslt1.1 package for
upgrade support (which should only be removed after etch release).

It could break some external stuff depending on old libxslt1 (thus
libxsltbreakpoint), but are there really any left outside of debian ?

So, what do you think ? Should I just leave it the way it is now or try
to make it cleaner ?

At the same time, should I do the same with libxml2 and name it libxml2-2 ?

Mike


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Graham Wilson

2005-08-11, 5:55 pm

On Thu, Aug 11, 2005 at 07:41:08PM +0200, Mike Hommey wrote:
> Now that no package depend on it, I am going to remove it, but that
> leaves a libxslt1.1 package alone, not really respectful of the debian
> standards for package naming.


How is it not respectful of Debian standards for package naming?

> So, what do you think ? Should I just leave it the way it is now or try
> to make it cleaner ?


Are there any functional or practical reasons to change the package name
back to libxslt1? If not, I don't see any need to change it.

--
gram


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Mike Hommey

2005-08-11, 8:49 pm

On Thu, Aug 11, 2005 at 01:40:41PM -0500, Graham Wilson <graham@mknod.org> wrote:
> On Thu, Aug 11, 2005 at 07:41:08PM +0200, Mike Hommey wrote:
>
> How is it not respectful of Debian standards for package naming?


"The run-time shared library needs to be placed in a package whose name
changes whenever the shared object version changes. The most common
mechanism is to place it in a package called librarynamesoversion, where
soversion is the version number in the soname of the shared library"

soname is libxslt.so.1

Mike


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Steve Langasek

2005-08-12, 2:55 am

On Thu, Aug 11, 2005 at 07:41:08PM +0200, Mike Hommey wrote:
> I'm about to remove the libxslt1 package, which has been created a long
> time ago for backward compatibility, when upstream did screw up ABI and
> removed support for the libxsltbreakpoint library.


> Now that no package depend on it, I am going to remove it, but that
> leaves a libxslt1.1 package alone, not really respectful of the debian
> standards for package naming.


> I was wondering if I should come back to good practice and provide a
> libxslt1 package with the library, and a dummy libxslt1.1 package for
> upgrade support (which should only be removed after etch release).


> It could break some external stuff depending on old libxslt1 (thus
> libxsltbreakpoint), but are there really any left outside of debian ?


> So, what do you think ? Should I just leave it the way it is now or try
> to make it cleaner ?


I think leaving it as-is would be the better option. The ideal state is to
never have to reuse a library package name for something with an
incompatible interface; which is exactly what you would be doing here, so
I can only see that being justified if you expect a future upstream version
to have libxslt1.1 as the soname.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon@debian.org http://www.debian.org/

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com