On Wed, Sep 24, 2008 at 02:16:22PM -0400, Jorge Arellano Cid wrote:
On Wed, Sep 24, 2008 at 05:44:51PM +0200, Johannes Hofmann wrote:
On Tue, Sep 23, 2008 at 07:11:03PM -0400, Jorge Arellano Cid wrote:
On Tue, Sep 23, 2008 at 02:54:10PM +0100, Jeremy Henty wrote:
On Tue, Sep 23, 2008 at 07:52:07AM +0200, Andreas Kemnade wrote:
Currently you need to download three tarballs to compile dillo (fltk,dw,dillo). I doubt that any linux distribution has fltk2 packages at the moment. (and also not openembedded) What's the plan about that?
FLTK2's API is still not frozen, and its ABI does change quite often so we will have to supply the tarball ourselves. It would be simplest just to keep a copy of the right FLTK2 snapshot on the dillo site under a link saying "use *this* version". The problem is not that distros won't supply packages, the problem is that they *will* and it might be the wrong version. (Expect "I upgraded FLTK2 and Dillo crashed" reports!)
The dw package is an awkward case. I think we should bite the bullet and either move it inside dillo2 or make it an independent package that the user installs and have dillo2 find and use the installed dw (and lose the dw-testbed symbolic link).
Thoughts?
I'd move dw2 inside dillo2's tree (as it was before), and have a recommended FLTK2 tarball in our site.
That sounds good!
OK, dw2 is now inside the dillo2 tree.
CVS updated and also the directions in cvs.html.
Please check and test.
Yes, it works fine! Cheers, Johannes