-
Notifications
You must be signed in to change notification settings - Fork 5
/
patch.txt
80 lines (49 loc) · 2.6 KB
/
patch.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
Patching(1) microemacs Patching(1)
PATCHING
This page describes how to patch a MicroEmacs installation with a later
release without re-installing.
Windows
Windows requires careful patching in order not to disturb the registry
settings The following procedure should be followed.
* Move to the jasspa directory, c:\ProgramFiles\JASSPA\Microemacs.
* COPY the executable me32.exe to a backup, you MUST copy the file
otherwise the registry settings will change. DO NOT MOVE THE FILE.
copy me32.exe me32_2002_12.exe
* Save the macros directory, these may be moved i.e.
rename macros macros_2002_12
* Unpack and install the new Windows executable and COPY over the
original executable that was previously backed up i.e.
copy c:\path-to-executable\me32-win32-20040108-rc1.exe me32.exe
* Create a new macros directory and install the macros into this new
directory, do this manually or using a utility like WINZip.
mkdir macros
cd macros
unzip c:\path-to\memacros-20040108-rc1.zip
* The new version of MicroEmacs will now operate with the old
installation environment. You may return to the old release by
reversing the steps to patch the installation.
UNIX/Linux
For *NIX package installations then patching is a little easier. The steps
are defined as follows:-
* Move to the jasspa directory.
cd /opt/jasspa/bin
* Save the original executable.
mv me me_200212
* Unpack the new executable and make it executable.
gunzip me-sun-solaris-20040108-rc1.gz
mv me-sun-solaris-20040108-rc1 me
chmod a+x me
* Save the existing macros directory.
cd /opt/jasspa
mv macros macros_200212
* Create a new macros directory and install the new macros:-
mkdir macros
cd macros
unzip /path-to/memacros-20040108-rc1.zip
* Installed packages are built with the install path built into the
executable, this may be different from the patch version of the
executable so the environment variable $MEINSTALLPATH(5) may be
defined in the environment with the macro installation search paths.
SEE ALSO
$MENAME(5), $MEINSTALLPATH(5), Company Profiles, Installation, File Hooks,
File Language Templates, User Profiles.