On 30/05/2005, you wrote:
I'd like to ask a more general question regarding the porting effort.
As we all have seen, activity died down after an initial euphoria.
This is dangerous as it might lead to a complete standstill.
This is partly (mostly?) my fault, my personal life got in the way of the
porting effort, for wich i apologise.
Therefore, the question is this: Currently, work is
underway to get the
dependencies ported. But in the very early stages, some of them aren't
really needed. So theoretically, work could be started on the low-level
parts of OpenOffice itself, for example the build environment and SAL,
resolving dependencies as they come up, maybe even creating "dummies"
for seldom-used functionality (for example, I've never used any USB
stuff with OpenOffice).
Agreed, this was actually the original idea, except we started/tried to
start with things that could be usefull to other projects (lubusb/sane in
itself is in my opinion a worthy project, as it would provide OS4 with
scanner support for hundreds of scanners), but maybe we should review these
Also, we really need to start using the CVS, so that when people disapear
their work doesn't
Ok, that's just food for thought.
BTW, OOo builds via dmake, which we already ported (SNAP also builds
with dmake). It just depends on newlib V3 which will be in the next
Theoretical question, could dmake run/build on classic and would it be worth
A fool-proof method for sculpting an elephant: first, get a huge
block of marble; then you chip away everything that doesn't look
like an elephant.
Hoge Buizemont 168
9500 Geraardsbergen, Belgium
Mobile: 0032 (0)479/46 45 74