[Brian May, 2016-05-01] > > please don't use python- prefix, use mkdocs-bootswatch. Note that binary > > package is "mkdocs" > > Ok, so I just call both source *and* binary packages mkdocs-bootswatch > and mkdocs-bootstrap then?
yes please > mkdocs was required for a DPMT package - django-rest-framework - and > this is the only reason I bother to package it. It is already in DPMT. we do not add libfoo package to DPMT (written in C/Perl/whatever) if its Python wrapper "foo" module requires it. We do not maintain gcc even though it's required by a lot of our packages. I'm sorry, but IMO one of the main reason of having teams in Debian is to group people interested in similar topics. I don't want to touch Perl or JavaScript and I'm grateful to people who maintain libraries for these languages for me. Someone long time ago decided to create a team to maintain Python modules, this team already has so many packages that almost nobody reads -team mailing list so I don't want to make it even worse (and scare these few people who still read it) and add Python applications or $UGLYLANG libraries there. If someone wants to package python-bar that requires bar-perl, IMO the best way (especially when you don't have that great Perl knowledge) is to join Perl team to help you maintain bar-perl and encourage Perl Team guys to maintain python-baz within our team if their baz-perl needs python-baz > I tried to get access to PAPT (so I could fix another package), however > so far haven't got a response. I guess I missed your request email on this mailing list, sorry. Let me know if you're still interested > I would sooner maintain them in collab-maint rather then PAPT, because I > don't really want to have to convert my git repositories to > subversion. I believe subversion is still required by PAPT. it is -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
