Debian version strings: If you are on the 0.9 branch you have to make clear that your package is smaller than "0.9.0-1". Your "0.9.0-devel+git20121104-makson*" > 0.9.0. So I would use something like "0.9.0~20121104-0ubuntu0makson1" on Ubuntu and 0.9.0~20121104-1" on Debian.
wxWidgets: wxwidgets2.9 might never be part of Debian, since it is the current wxWidgets development branch. Debian will switch to wxwidgets2.10 when it gets released by upstream. Development of end-user-software should be based on wxwidgets2.8. wxwidgets2.9 could be part of a wxwidgets-unstable package only available in Debian/sid, but this is unlikely to happen and it would mean that desurium could never join Debian/testing. CEF: I don't know CEF but you should try to contact CEF-upstream and let them merge the changes needed for desurium. Having libcef and libcef-desura would mean code duplication which should be avoided if possible. Since libcef does not exist on Debian or Ubuntu it might be possible to include the changes in a "libcef" package if they would brake no other packages using libcef. cURL: If possible add c-ares support into upstreams curl. If not include a patch in Debians curl package. If that patch would break things, fork curl or remove dependency on c-ares from desurium. Forking means code duplication means worse maintainability. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
