Re: leechcraft (closes ITP bug, 33 days have passed)

While I think this package is interesting, I do not intend to sponsor it. That said, here is a review of the source package: I'm not sure it is appropriate to change the ABI names used by upstream to a Debian-specific one. If you want to change the library names that should be done upstream.

Re: leechcraft (closes ITP bug, 33 days have passed)

Hi, Boris Pek tehnic...@yandex.ru writes: I am looking for a sponsor for my package leechcraft. I probably won't sponsor the package, but I was wondering if it is really necessary to build 53 binary packages (if I did not miscount)? Regards, Ansgar -- To UNSUBSCRIBE, email to

Re: leechcraft (closes ITP bug, 33 days have passed)

While I think this package is interesting, I do not intend to sponsor it. Thanks a lot for such detailed review! And for possibility to practice in English. =) That said, here is a review of the source package: I'm not sure it is appropriate to change the ABI names used by upstream to a

Re: leechcraft (closes ITP bug, 33 days have passed)

Hi, I probably won't sponsor the package, but I was wondering if it is really necessary to build 53 binary packages (if I did not miscount)? The short answer: yes, it is. Here I can cite the description from my first message: LeechCraft is a free open source cross-platform modular

Re: leechcraft (closes ITP bug, 33 days have passed)

Hi, Boris Pek tehnic...@yandex.ru writes: I probably won't sponsor the package, but I was wondering if it is really necessary to build 53 binary packages (if I did not miscount)? The short answer: yes, it is. Here I can cite the description from my first message: LeechCraft is a free open

Re: leechcraft (closes ITP bug, 33 days have passed)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Boris, On 08.11.2011 15:58, Boris Pek wrote: qxmpp, Qxt, eiskaltdcpp, miniupnpc, parseUri, lightbox, hunspell/myspell (and anything else in 3rdparty or third-party dirs) are either already in Debian or should be packaged separately, you

Re: leechcraft (closes ITP bug, 33 days have passed)

[...] You can use wildcards in .install files like these: [...] usr/share/leechcraft/translations/leechcraft_poshuku_*.qm [...] I have just found again the reason to not use it. Available wildcards are very primitive. And they will affect to sub-plugins. For example:

Re: leechcraft (closes ITP bug, 33 days have passed)

Hi, I probably won't sponsor the package, but I was wondering if it is really necessary to build 53 binary packages (if I did not miscount)? The short answer: yes, it is. Here I can cite the description from my first message: LeechCraft is a free open source cross-platform modular

Re: leechcraft (closes ITP bug, 33 days have passed)

Hi, qxmpp, Qxt, eiskaltdcpp, miniupnpc, parseUri, lightbox, hunspell/myspell (and anything else in 3rdparty or third-party dirs) are either already in Debian or should be packaged separately, you should not include them in the binary package or tarball. You are really mistaken at this

Re: leechcraft (closes ITP bug, 33 days have passed)

On Tue, 08 Nov 2011 23:23:06 +0200 Boris Pek tehnic...@yandex.ru wrote: This seems to be a bit excessive. There is no real use in having many tiny packages for every function; please keep in mind that this will make the Packages index even larger (which also affects users that do not

leechcraft (closes ITP bug, 33 days have passed)

Dear mentors, I am looking for a sponsor for my package leechcraft. This is repeated message. It have passed: - 33 days from the first message (03 Oct 2011) - 26 days from the last repeated message (10 Oct 2011) Last discussion messages: