[Pkg-mono-devel] maintaining older version of cil libraries

[Sam Clegg]

Yesterday I uploaded a new version of boo (0.8.0) to unstable.
However, there is at least one package which broke due to assembly
version changing from 1.0.0.0 to 2.0.0.0:

http://bugs.debian.org/458835

Of course, this could have been avoided if I had just run apt-rdepends
first :)

I was just wondering what the correct course of action is to fix this.

My initial plan is to create both boo1 and boo2 source packages
and build the old package 'boo' from the boo1 sources.  This would fix
the current banshee packages (which depends on boo (>= 0.7.6.2237) to
access the boo 1.0 libs).

Next I would create both libboo2.0-cil and boo2 from the boo2 sources,
which means that in the future packages such as banshee would end up
depending on libbooX-cil and this kind of problem shouldn't occur again.

Does this make sense?  

I am also planning on uploading boo/debian and boo/debian
to the pkg-mono repository and moving maintainership to the pkg-mono
group.


-- 
sam clegg
:: sam at superduper.net :: http://superduper.net/ :: PGP : D91EE369
$superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-mono-devel/attachments/20080103/6bf66d83/attachment.pgp