Dom Lachowicz wrote:
>> 1) Check this into HEAD once it's closer to being
>> ready.
>> 2) Create a branch for this?
>> 3) Maintain a patch set publicly somewhere?
>> 4) Fork AbiWord?
>
> FWIW, my preferences are presently (in order from most
> preferable to least preferable):
>
> 1, 2, 4, 3.
>
> I could be convinced of branching and then merging
> back, provided that the branch was extremely short
> lived. Like, less than a month.
I vote for 1. If it is not in the tree, it won't make it. Look at Marc
"double-graphics" patch and "reveal codes". They are not in the tree, so
we don't have them.
The glib dependency is a non issue on MacOS X as we already have it.
And depending on glib allow to bring enchant :-)
Hub
Received on Tue Feb 21 16:51:36 2006
This archive was generated by hypermail 2.1.8 : Tue Feb 21 2006 - 16:51:37 CET