Re: [cl-debian] Re: Bug#446971: ITP: zpb-exif -- Common Lisp package to access EXIF metadata
Hi Pierre! On Wed, 17 Oct 2007 04:24:51 +0200, Pierre THIERRY wrote:
Scribit Luca Capello dies 17/10/2007 hora 04:08:
Could you also X-Debbugs-CC: the CL-Debian mailing list [1] the next ITP about CL software, please?
No problem.
I guess this should be in the CL-Debian policy ;-)
I'd call the binary cl-zpb-exit,
Yes, that's what I did, as with my other packages. I try to have source package name as close as possible as the original project name and the binary package name beginning with "cl-".
While I guessed that, I wrote it anyway to be sure (and I was too lazy to wait for your package link and check). Thank you for the package! Thx, bye, Gismo / Luca
Scribit Luca Capello dies 17/10/2007 hora 04:58:
I guess this should be in the CL-Debian policy ;-)
After discussing a bit with maintainers involved with Perl or Python packaging, I wonder if our policy shouldn't be extended a bit and made mandatory for Common Lisp packaging. Being mandatory ensures packages will be consistent, which is better both for maintainers (they know for sure where to put things and how to name things) and users (they know fore sure where to find things and how they would be named). Methodoligocally, Pierre -- nowhere.man@levallois.eu.org OpenPGP 0xD9D50D8A
Hi Pierre! On Wed, 17 Oct 2007 15:00:56 +0200, Pierre THIERRY wrote:
Scribit Luca Capello dies 17/10/2007 hora 04:58:
I guess this should be in the CL-Debian policy ;-)
After discussing a bit with maintainers involved with Perl or Python packaging, I wonder if our policy shouldn't be extended a bit and made mandatory for Common Lisp packaging.
I think that because of clc the "policy" is already mandatory and I don't know of any CL package that doesn't follow it.
Being mandatory ensures packages will be consistent, which is better both for maintainers (they know for sure where to put things and how to name things) and users (they know fore sure where to find things and how they would be named).
Fully ACK. The "Common Lisp in Debian Manual" [1] written by René should be the start for the policy, IMO. Comments, suggestions, opinions? Thx, bye, Gismo / Luca Footnotes: [1] http://cl-debian.alioth.debian.org/clid/clid.html/
Scribit Luca Capello dies 18/10/2007 hora 21:55:
I think that because of clc the "policy" is already mandatory and I don't know of any CL package that doesn't follow it.
You're free not to use clc, and how you package your package exactly is left at the maintainer's will entirely. The policy should state explicitely, independently of the tool, where files should be installed, what actions should be triggered in maintainer scripts and how to deal with dependencies.
The "Common Lisp in Debian Manual" [1] written by René should be the start for the policy, IMO.
And having dh_lisp obviously helps. Quickly, Pierre -- nowhere.man@levallois.eu.org OpenPGP 0xD9D50D8A
participants (2)
-
Luca Capello -
Pierre THIERRY