-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Damien
damien clochard wrote: | Le Mardi 29 Mars 2005 17:38, vous avez écrit : | |>The bug title and owner were already changed... Did you do this on |>purpose? Probably not as I forgot to Cc [EMAIL PROTECTED] (so did |>you btw) to make it more clear. |> | | | Sorry about that, my mistake.... | A friend of mine told me there was a RFP request for tiny erp, so i just send | the mail to [EMAIL PROTECTED] without checking any further... | | |>Do you want to co-maintain tinyerp? | | | Yes sure... | | i think i've done a good part of the job already , but this is one of my first | debian package and i'm sometimes lost in the debian policy mysteries ;) | | Here's what i've done : | http://debian.dalibo.org/dists/sarge/main/binary-all/tinyerp-client_2.0-6_all.deb | http://debian.dalibo.org/dists/sarge/main/binary-all/tinyerp-server_2.0-3_all.deb | | i'd be glad to know what you think of theses packages
It would be better to judge if I would have access to the source packages (*.tar.gz, *.dsc and *.diff.gz).
| By the way here's the small problems i encountered during this 'debianization' | | * there's no init.d script for the server , i had to write it
Yes, I noticed this too.
| * the client needs to be launched from the /usr/lib/tinyerp/client directory , | so i put a trivial script in /usr/bin to launch it easily
Yes, I had a similar solution in mind. We will have to write a manpage for it too ;-)
| * i had to separate images from python files to avoid images in /usr/lib
Well, I'm not so sure to put them in /usr/lib, I thought of using /usr/share...
| * i made xpm icons so that update-menus is fully fonctionnal
Good idea, but I want to see the source ;-)
| * the '#!/usr/bin/python' is omitted in many .py files
I think this is intentional: they are only used for importing them.
What did you do with pydot (seperate license)?
In any way I like to see the source package (you could maybe upload it to mentors.debian.net?).
| I guess the easy way to co-maintain tiny-erp would be to split the task in | two. You maintain the server and i'll take the client , or vice-versa... | Does it sounds reasonable to you ?
I thought more of actual co-maintainership [1] for both of the packages. This is certainly preferable if you are not an official Debian Developer (yet?) ... then you don't have to search for a sponsor :-)
Cheers
Luk
[1]http://www.nl.debian.org/doc/developers-reference/ch-pkgs.en.html#s-collaborative-maint -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCSltb5UTeB5t8Mo0RAj0JAKClP5YxsdRNw+Ohf/jWZJLtMiyHOACfcdm3 QVTc1ut6UoCiv9cpeAmjS4s= =zKJ5 -----END PGP SIGNATURE-----