Darren Reed wrote:
> For a long time, various emacsy things have been delivered
> as a part of SUNWspro (Sun's compiler package for Solaris),
> the latest being 21.4.12 delivered in SS12.
> 
> Has this project been in communication with the the developers
> of SUNWspro to ensure that we don't get 2 emacs installations
> when we install SUNWspro on a system with SUNWemacs*?
> 
> Are there any interface problems for SUNWspro if it executes
> "emacs" (consider SS12 being used with SUNWemacs*) and
> ends up with a version of emacs running that it didn't deliver?
> 
> Darren
> 

There's not a conflict with this case. The emacs delivered by
SUNWspro is Xemacs, not GNU emacs. Looking in the bin directory
of SS12, I see xemacs, and xemacs-mule, which are symlinks to
../contrib/xemacs-21.4.12. So the command SUNWspro will be
issuing is 'xemacs'.

Not This Case But:
    When Xemacs does get integrated into SFW, there shouldn't be
a conflict there either. Even today, SUNWspro is only one way
in which a Solaris user is likely to have xemacs in their path,
and probably not even the most likely such way. Many (most?)
Xemacs users have a locally installed xemacs in their PATH
ahead of the SUNWspro one. I'm sure the Sun Studio group has
already had to grapple with this issue.

- Ali

Reply via email to