So, while I'm looking :)
At the moment, the simias software autobuilds into two different RPMs:
simias and ifolder3-enterprise. These are both building very similar
RPMs from basically the same source, as far as I can tell:
* the scripts to autobuild are effectively a cut'n'shut with minor
differences in naming and versioning,
* the spec files again are cut'n'paste, with more differences than
the autobuild but doing quite similar things,
* the autogen.sh has a flag --with-runasclient in simias
The runasclient flag is mildly interesting, but doesn't really seem to
change that much in the source:
* SimasService.cs gets created from a WSDL definition in two
different ways and there's an extra SimiasService2.cs, depending
on which way the flag is blowing,
* a different mono*.config file gets installed depending on the flag.
It seems to me this differentiation between client and server really
ought go; indeed the code already determines the client/server behaviour
at run-time in some places (e.g., core/Common/Defaults.cs).
Is there anything else I'm missing?
Cheers
Alex.
_______________________________________________
ifolder-dev mailing list
ifolder-dev@forge.novell.com
http://forge.novell.com/mailman/listinfo/ifolder-dev
