Re: ATTN: wv tagged, branched

>
> I'm going to be doing a lot of janitorial work on wv
> over the next few days that will entail a major
> overhaul of its dependency list, build structure, etc.
> I'm hoping to slim down the code base, reduce the size
> of the package, clean up the build system, and (most
> importantly) introduce a dependency on libgsf instead
> of libole2. I don't forsee breaking the API during
> this transition.
>
> However, in order not to screw over the AbiWord folks
> I've created a branch that you all can work against.
> It is called "wv-1-0-0-STABLE". I suggest that Abi's
> build instructions be updated to refer to that branch,
> and that any inconvenienced people (most importantly,
> the Win32 folks) stick to that branch for the time
> being. I will be committing my changes to HEAD.
>
> Please remember that wv is its own project that just
> happens to live in Abi's CVSROOT and needs to evolve
> on its own terms sometimes.

HI Dom,
       This seems like a good time to bring up something that has been on
my mind for a long time.

There is lots of really good code in glib and libgsf. The longer we put
off depending on these the longer go without the benefits of this code.
(Like string to intgeger maps (quarks) and network transparency for
loading documents.

Is this the right time to introduce a cross platform dependency on these
libs?

Cheers

Martin

>
> Best,
> Dom
>
>
>
> __________________________________
> Do you Yahoo!?
> Make Yahoo! your home page
> http://www.yahoo.com/r/hs
>
Received on Sun Apr 17 23:54:59 2005