Howdy, On Tue, Apr 22, 2003 at 10:05:08PM +0200, Gregor Hoffleit wrote: > retitle 190184 ITP: chandler -- personal information manager for email, > calendars, contacts, tasks etc > thanks > > I'm interested in this. I'm still working my way through the build > process of Chandler, and indeed it seems to have quite a few pitfalls. > > According to the release notes, I guess it won't make much sense > currently to include Chandler packages in Debian main. Instead, I would > provide experimental packages first, unless the foundation of Chandler > is more mature. > > Anyhow, if I look at the dependencies of Chandler 0.1, there seem to be > quite a few issues that have to be cleared up first. E.g. I would need > > - a libwxgtk2.4-python2.3 package,
You'll get the above in sid when python2.3 is the default there. Since chandler appears to be aiming for "unstable everything" I presume that is likely to happen at around the time chandler is ready for real users too. Building wx packages locally that use python2.3 should be easy enough, but there is no easy mechanism to support both as 'official' uploads (in a single dist pool) in the existing packaging. Given the mess multiple versions of png &c is causing, I'm not really sure I would want to see that either. We could have python2.3 packages in experimental maybe, but I'm going to need a *big* compile farm if I'm to support all the combinations of gtk/python/libfoo that wx could possibly be built with. Robin, can you shed any light on the python2.3 dependency or projections for a broader release of chandler? thanks, Ron > - a zodb4 package (there's an ITP for zodb3, but Chandler employs zodb4, > which is a major new version that's just in development) > - a new version 2.0.4 of the egenix-mx-base is needed > - appearently jabber.py also has been forked off in Chandler > > Gregor