Bug#308339: Wrong source package name

[Arnaud Vandyck]

Fri, 13 May 2005 00:02:58 +0200,=20
Jeroen van Wolffelaar <jeroen@wolffelaar.nl> wrote:=20

> On Thu, May 12, 2005 at 11:51:02PM +0200, Arnaud Vandyck wrote:

[...]

>> You mean creating a tarball with the two different versions of the
>> lib?!  And why do you want we change the name of the source package
>> when the first one is removed?
>
> What I mean is to indeed have different binary package package names,
> the libraries are incompatible anyway.
>
> My only point is to have the *same* _source_ package name. This does
> mean that the old library will get deleted on upload, so that all
> depending packages will need to be updated in about the same
> timeframe.

So it's the responsability of the maintainer of a library to know which
packages are linked against its lib? And if he drop a library, he could
drop dependencies for some packages?

The log4j transition took more than a year!

> This usually should be easily doable, and when doing so, it means less
> work for all and no obsolete packages hanging around for long times --
> no need to ask for removals, and a swift transition.

No need for removals also means that only the maintainer decide if he
can remove the package or not! No one can voice against the removal of a
particular version of a lib. Those transitions are not always easy.

> This is of course of medium/long-term importance, and of course this all
> is to be decided how to precisely do when the situation arises.

OK, it's if medium/long-term importance, I can understand your point,
but the way I understood your bug report:

    =C2=ABLibrary packages should not have a version-specific source-package
    name[...]=C2=BB

It's not a question, or a proposal, it seems like a request (but maybe
my english is not that good and I don't understand 'should' has I
should) or an order! Thanks to clarify.

If it's a medium/long-term proposal, you can help me understanding who
you'll solve the version of two binary packages with the same source?
Will I have to play with extra debian files or is there a way to decide
the version number from the debian/changelog file? Do we have to rebuild
all these source packages with tarballs inside? If it's the case, maybe
it's only me but it takes me more time to deal with such packages and
it's the case when I have to patch them. Also, dealing with patches from
two different upstream sources seems funny ;-)

Cheers,

--=20
  .''`.=20
 : :' :rnaud
 `. `'=20=20
   `-=20=20=20=20
Java Trap: http://www.gnu.org/philosophy/java-trap.html