minor readme update
[mharc.git] / README.FSF
CommitLineData
190cf5a4
IK
1Note: This repo is prone to being force pushed because, commits are
2meant as documentation of whats changed from upstream and whats been
3deployed for significant periods, so sometimes its better to edit them
4as they are developed.
5
76fcbc18
IK
6We do not use use the provided read-mail to process spools and we don't
7use lists.def. We bypass that part of mharc and call web-archive
8instead.
e9187eaf 9
76fcbc18
IK
10This repo is based on mharc 0.7.3 release. The .dist files are all the
11upstream except changing path names of standard utilities to match the
190cf5a4 12distro. I dunno what those are about.
2ea8f66b 13
76fcbc18
IK
14The .dist files should never be changed except when upgrading to new
15upstream version (and there does exist a non-release snapshot we should
16upgrade to).
17
18Any file with a correspond .in version should never be manually edited,
19instead generated from the .in file by running make configure. Note,
20make configure must be run from /home/mharc (checkout into that
21directory on your local system).
22
f6787fa8 23The lists.fsf.org branch should be rebased to any changes from master, like this:
76fcbc18 24
f6787fa8 25git checkout lists.fsf.org
76fcbc18
IK
26git rebase master
27# if there are merge conflicts, manually merge any .in files, then
28make configure
29git add .
30git rebase --continue
31git push -f
32
33Then on lists.fsf.org:
34
35su mharc
36cd
37git fetch
f6787fa8 38git reset --hard origin/lists.fsf.org
190cf5a4
IK
39
40
41To update existing lists headers, the only way namazu supports is to
42rebuild the index, but that takes about 3 days. Instead, I put a random
43unique string into the header where the list name goes, copied it to
44/tmp, su mharc, cd to the html dir, then ran this:
45
46for x in */NMZ.head; do sed "s/gachJefyeonJoa/${x%/*}/g" /tmp/NMZ.head>$x || { echo failed on $x; break; } ; done
47
48This process can be repeated for more changes.