Am 29.8.07 um 08:14 schrieb Arthur Barrett:
> Jens,
>
>> A MacCvsX 3.3b1 release is available on sourceforge. MacCvsX now
>
> Thanks and congrats!
>
> Is this PowerPC ? I assume you are still using that powerpc specific
> library (I've temporarily forgotten the name)?
Yes, MacCvsX is using PowerPlant as it's underlying application
framework and there's about zero chance to make this run natively on
Intel :(
However, since cvsnt is a separate tool, it would be perfectly
possible to embed a Universal binary of the cvsnt tool + libs. That's
actually a good point - after all, it's the cvsnt tool that does most
of the 'real' work.
>
>;> - There is a conflict if you have cvsnt installed on your computer.
>
>> defaults write org.gnu.MacCvs P_UseCvsnt -boolean false
>
> Wouldn't it be possible to create a symbolic link from the cvsnt in
> the
> Resources folder to the public one?
>;
> Do you know when the conflict occurs (which "public" version and which
> version you are including in resources)?
No, I haven't dived too much into this problem yet - I just
experienced once that MacCvsX wouldn't load the pserver tool and
realized it was due to a conflict between the library installed in /
usr/lib and the on inside the MacCvsX application package.
(The version included is 2.5.03 Build 2210 - that was the one I
started out with and it seems to do all the stuff MacCvs requires)
I don't really like the idea of a symbolic link inside the resources
folder, but maybe it would make sense to have a preferences checkbox
to use cvsnt from another location. MacCvs would then ignore the
built-in tool and just rely on the standard installation to be
'complete'. Sounds sensible...
</jum>
.
