Re: uploaded libstatistics-descriptive-perl
Joachim Breitner dijo [Sat, Mar 12, 2005 at 01:42:13AM +0100]:
> > This is the same thing that Gunnar did for the
> > libspreadsheet-writeexcel-perl package just a few days ago.
> He did? Did he already try an upload?
It was not a couple of days, but a couple of weeks ago. Yes, I have
the habit of renaming packages in order to keep them compliant with
the policy - remember that after all our policy just "documents
current practice", therefore, if most Perl modules are called
libfoo-bar-perl and one is called just foo-bar, then it is potentially
breaking policy ;-)
> AFAICT, chaging the source name will make the scripts treat the package
> as a new one, meaning that it will have to go through NEW, which takes
> quite some time these days. Also, you will have to force
> an .orig.tar.gz-upload even though it is not a -1 version. And all kinds
> of other horrible stuff :-)
Yes, it has to pass through NEW, although its transit has been quite
smooth in the five or so cases I have done so (couple of days). I
actually filed bugs against ftp.debian.org requesting the removal of
the old package just after uploading, but Andreas Barth (IIRC) told me
this was unnecessary, as they saw a different source package producing
the same binary package - Just, of course, document it in your
changelog so they find it more easily.
> OTOH, there is no problem in having a differing source name, and for
> library packages, this is not uncommon. I'd strongly recomment not
> changing the source name, but I'm interested in what Gunnar has to say.
It is not necessary, of course... But then again, it is not necessary
for my source package libfoo-bar-perl to change the name if it is
generating the Python baz module ;-) It is just a matter of clarity.
Greetings,
--
Gunnar Wolf - gwolf@gwolf.org - (+52-55)1451-2244 / 5554-9450
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
Reply to: