RFC: Yorick (scientific interpreted language) & plug-ins
Hello,
I am adopting Yorick and packaging add-ons for this interpreted language
aimed at scientific number crunching, data visualisation etc.
I know the packages need more work (in particular concerning the
copyright files, removing commented-out dh_*lines in rules and
rebuilding under sid), so I am not requesting a detailed review, but I
think advice on the following few questions would be timely:
* package granularity: I have currently 7 add-on packages (one more
coming soon), each one rather small (few 100K each) but coming from a
different upstream and depending on different libraries (like libtiff,
zlib and other). Should I keep these add-ons separate or compile a
single yorick-addons package? (I need this question sorted out before
I start filling ITP bugs).
I have the reversed question for the upcoming package (yeti,
http://www-obs.univ-lyon1.fr/~thiebaut/yeti/yeti-6.0.2.tar.gz )
which is indeed 4 plugins: a set of general purpose utilities, and
wrappers for regex functionnalities, libtiff and libfftw2. If I stick
to one package per plugin, should I split this one?
There are also a couple of very specialised plugins (not yet
packaged), I think I would definitely make distinct packages for
those.
* name space: I prepended yorick- to each upstream name to help users
find out what add-ons are available, comments welcome. Some upstream
names can really not be left untouched: e.g. "curses" for the curses
wrapper... Of course this question is resolved if I go for a single
package.
* version numbers: upstream Yorick is named "2.1.02" although it is very
regularly updated on cvs. I'm currently sticking to 2.1.01cvs<date>
to be ready when an official 2.1.02 is released. The upstream author
(and former Debian packager) is ready to create a CVS tag to give some
substance to the version that will eventually go into Debian, even if
not making a point release. Do you have any piece of wisdom with that
respect? (Note that the CVS version contains changes I asked for for
better Debian policy conformance, so I don't want to package the
already released version 2.1.01).
If I go for grouping all the add-ons in a single package, what version
numbers should I use for it?
The packages are available through the repository:
deb http://www.mpe.mpg.de/~paumard/debian/ sarge main
deb-src http://www.mpe.mpg.de/~paumard/debian/ sarge main
The actual files are stored in:
http://www.mpe.mpg.de/~paumard/debian/dists/sarge/main/binary-i386/
http://www.mpe.mpg.de/~paumard/debian/dists/sarge/main/source/
Thanks for your time and attention,
Best regards, Thibaut.
Reply to: