Στις 27-05-2013, ημέρα Δευ, και ώρα 21:00 -0400, ο/η wp mirror έγραψε:
Dear Ariel,
Some time ago, I generated a DEB package named `mwxml2sql_0.0.2-1_amd64.deb'. It works very well, and was the source of the patches that I submitted upstream. Now that I have learned that you welcome such patches, it occurs to me that you might want the DEB package as well. If so, then there are a number of things we should discuss.
- Naming
Your other DEB packages have names like:
mediawiki_1.19.6-1_all.deb mediawiki-extensions-base_3.3_all.deb mediawiki-math_1.0+git20120528-7_amd64.deb
For naming consistency, would you like the `mwxml2sql' package to be renamed something like
mediawiki-mwxml2sql_0.0.2-1_amd64.deb
Yes, that sounds like a reasonable naming scheme.
- ITP
Debian policy requires that new packages first be announced with an Intent-To-Package (ITP) bug report. Then a `Debian Developer' may or may not step forward to sponsor the package for inclusion in a Debian distribution.
Do you have someone in-house, who is serving as a `Debian Maintainer'? If so, could you introduce us?
One person on our team was already a member of the Debian project when he came to us but he's not in charge of our packages there. From looking at http://packages.debian.org/sid/mediawiki-extensions-base it seems we want to get in contact with Romain Beauxis or Thorsten Glaser and see how to proceed.
- Architectures
All my systems are AMD64. Whereas `mwxml2sql' contains C language programs, and whereas Debian is a binary distribution; a set of `mwxml2sql' DEB packages should be prepared, one for each architecture. Do you have a way of generating DEB packages for other architectures?
All I've got is amd64 as well. But it looks like Debian does this for us: see http://www.debian.org/doc/manuals/maint-guide/build.en.html#autobuilder Hmm I really have no idea what will happen to some of these on a 32-bit system, I should check that out in a vm sometime...
Ariel