Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11864 > unrolled thread
| Started by | Emmanuel Arias <emmanuelarias30@gmail.com> |
|---|---|
| First post | 2019-10-04 23:10 +0200 |
| Last post | 2019-10-04 23:10 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.maint.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Packaging a new Python library Emmanuel Arias <emmanuelarias30@gmail.com> - 2019-10-04 23:10 +0200
| From | Emmanuel Arias <emmanuelarias30@gmail.com> |
|---|---|
| Date | 2019-10-04 23:10 +0200 |
| Subject | Re: Packaging a new Python library |
| Message-ID | <yNCZQ-83Y-5@gated-at.bofh.it> |
El vie., 4 de oct. de 2019 a la(s) 18:00, Povilas Kanapickas (povilas@radix.lt) escribió: > > 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? Hello, Yeah from my point of view I think would be great create the package under team's umbrella. Will be easy get help and feedback from the team :-) Cheers > > Regards, > Povilas >
Back to top | Article view | linux.debian.maint.python
csiph-web