Hi Sebastiaan,

Il 30/12/22 10:09, Sebastiaan Couwenberg ha scritto:
On 12/30/22 09:28, Antonio Valentino wrote:
Il 30/12/22 07:01, Sebastiaan Couwenberg ha scritto:
On 12/29/22 23:43, Antonio Valentino (@antonio.valentino) wrote:
- - - - -
fd81b17f by Antonio Valentino at 2022-12-29T21:45:46+00:00
New pylibtiff package for command line utilities

- - - - -
[...]

- - - - -
f8c5bd23 by Antonio Valentino at 2022-12-29T22:40:46+00:00
Set distribution to unstable

You should target experimental for uploads that need to pass NEW to control when it get into unstable.

Thanks. I didn't think about the NEW queue.
Thinking better I'm wondering if it makes sense to split this package in the end. After all the new package only includes the entry-point scripts for 2 utilities included in the main one.
What is you recommendation in this case?

I prefer separate packages for scripts in /usr/bin, that avoids library-package-name-for-application lintian issues.

Plus you can then just install pylibtiff instead of python3-libtiff to get both which saves some typing.

I have now set the distribution to experimental.
Could you please upload for me?

cheers
--
Antonio Valentino

_______________________________________________
Pkg-grass-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel

Reply via email to