Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11865
| From | Povilas Kanapickas <povilas@radix.lt> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Packaging a new Python library |
| Date | 2019-10-04 23:10 +0200 |
| Message-ID | <yNCZQ-83Y-7@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Hi, I would like to package this Python library that is not yet in Debian: https://github.com/peterbe/premailer as a new version of the cppreference-doc package that I maintain has it as a build dependency. What would be the best organizational approach to do that? I could maintain the premailer package myself, but given the fact that many packages are maintained as part of the Python modules team, should I join the team and create the package under the team's umbrella? Regards, Povilas
Back to linux.debian.maint.python | Previous | Next | Find similar | Unroll thread
Packaging a new Python library Povilas Kanapickas <povilas@radix.lt> - 2019-10-04 23:10 +0200
csiph-web