On Wed, 2008-08-20 at 19:10 +0000, directhex wrote: > Sorry for the delay, forgot to subscribe to this bug.
Hi, Thanks for the information. > mono-tools upstream supports several HTML engines, so using gecko-sharp > (as with current Ubuntu packages) remains possible. However, the Debian > Mono team will no longer be linking mono-tools (or any other Mono > package) against gecko-sharp. The question therefore is a question of > preference - if Ubuntu developers such as yourself don't mind needing to > put in work on a merge whenever mono-tools is updated, then by all > means, keep webkit-sharp out of main. If syncing is preferred due to > lower admin overhead, then webkit-sharp will be required. I'd love to get rid of the diff, and it sounds like a good idea. Webkit is in main, but webkit-sharp isn't yet. I don't know what the policy is on language bindings. I'll try and see if it's possible to promote webkit-sharp early enough that we can sync without problems. > You may also want to look at the other non-webkit changes in 1.9-2 > (http://packages.debian.org/changelogs/pool/main/m/mono-tools/mono- > tools_1.9-2/changelog), but none of them are exactly vital. > > In either case, I'd feel much happier with 1.9-anything in Intrepid > compared to the obsolete 1.2.6 currently in there. If you want to go > ahead with the existing diff.gz, then feel free, it'll still produce > perfectly usable packages. That would be the second option, if we can't get the promotion in time. Thanks, James -- Please merge mono-tools 1.9-1 (main) from Debian unstable (main) https://bugs.launchpad.net/bugs/243093 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
