[384] in Release_7.7_team
emacs19
daemon@ATHENA.MIT.EDU (Mike Barker)
Thu Dec 14 16:09:51 1995
From: Mike Barker <mbarker@MIT.EDU>
To: release-team@MIT.EDU
Cc: miki@MIT.EDU
Date: Thu, 14 Dec 1995 16:09:42 EST
Problem Statement:
Miki has found that emacs18 can't be built with Solaris 2.4.
emacs19 is available.
So--when we move to Solaris 2.4 (with AFS 3.4) in general use, we need
to have the public ready to use emacs19.
I think we should upgrade the dec and rs6000 systems at the same time.
Possible parts of solutions:
1. Set up a DCNS locker with emacs19. Make what we expect to have
available next summer (assuming we get to Solaris 2.4 by then). Some
problems with this are that users must add a locker, dot files
etc. will have the locker "builtin".
2. Put emacs19 on the srvd. it may take a week of effort to install
and check common uses (e.g. discuss, mh-*, newsreaders, and other
elisp modes). will also involve checking for name conflicts
(e.g. emacsclient). must be done for solaris, dec, rs6000. can be
done as late as IAP as it will be a directory on the srvd without a
letter bump, etc.
3. change emacs18 startup banner to tell users that emacs18 will not
be available in future releases and they should take this opportunity
to begin familiarizing themselves with it.
Preferred solution: 2 + 3
Problem areas:
1. documentation updates can be done by summer?
2. training updates can be done by summer?
3. are there other common use applications, interfaces using emacs18
that we support/should provide help in converting?
4. how many groups (consulting, sipb, etc.) need to know that we are
changing from emacs18 to emacs19?
Any other comments?
Please respond by email. I'd like to have this issue settled before
the meeting next week and simply report it.
Thanks
mike
