[Pkg-mono-devel] Packaging of f-spot

[Anthony W. Juckel]

I've recently finished some preliminary packages for f-spot, but I 
wanted to pose some questions to this list before soliciting for a 
sponsor on debian-mentors.

I'm addressing this message here since I believe my questions focus more 
on specific Mono/CLR policies, rather than general Debian packaging 
policies.

First, f-spot contains a number of c libraries as well as the standard 
C# fare, so I'm wondering if it would be a good idea to split the 
library up into two packages: f-spot (Architecture: all) and libfspot 
(Architecture: any).  Secondly, since there isn't (at least to my 
knowledge) a formal Mono/CLR policy yet, I'm wondering what other's 
feelings are on packaging Mono binaries.  First, should a wrapper script 
be included, or is it preferable to rely upon the bin-misc support that 
is installed along with the mono packages?  Second, the default 
packaging of f-spot (simply using cdbs with little modification) wants 
to put f-spot.exe in /usr/lib/f-spot.  As this is a binary that can be 
executed directly (if bin-misc support for mono is enabled), I feel it 
should go in /usr/bin.  On the other hand, I've noticed that muine and 
monodoc both place .exe files in /usr/lib/{package}, so should I go that 
was as well?

Finally, I would like to thank the mono packaging team for all their 
work.  It is nice to have working and relatively current packages for 
mono and its associated libraries in unstable.

If anyone would like to download my f-spot packages, they are available 
(with some out-of-date mono cruft) at the following apt sources:

deb http://www.juckel.net/apt unstable/
deb-src http://www.juckel.net/apt unstable/
 

Anthony W. Juckel