Document Home | Document Index

 make a halibut release

This may seem a bit complicated, but it's a useful exercise for future reference, it may apply (mostly) to other cloned Git repositories.

git clone --recursive git://git.tartarus.org/simon/halibut.git

creates a directory halibut containing the Git repository embedded in a checkout. Save this in git-halibut-20170813.tar.xz (current date in the name) for possible future use.

• In the halibut directory, run git log and note the first 10 characters of the hash of the latest checkin (7ed66467ff in this case). This will be used as the version of halibut for which a release will be created.
• In the same directory, run the script in Git archive with submodules.
• Abandon the halibut directory and use the file generated in the previous step:

      cd ..
      rm -rf halibut
      tar xvf halibut-temp.tar.xz
      cd halibut-temp
  

• In this directory, it is possible to build a normal distribution.
  • Specify the version to be used (the hash noted above):

         sed -e '/NOVERSION/s//7ed66467ff/g' configure.ac -i
    

  • Prevent this version from being overridden later:

        sed -e '/^#define/s!$!*/! ; s!^!/*!' version.h -i
    

  • Generate a release:

        ./autogen.sh
        ./configure
        make dist-xz
        mv halibut-7ed66467ff.tar.xz ..
    

• Abandon the halibut-temp directory and use the file generated in the previous step:

      cd ..
      rm -rf halibut-temp halibut-temp.tar
  

• The file halibut-7ed66467ff.tar.xz is a usable release identifying itself as the correct version.

Document Home | Document Index