README.FSF

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