mirror of
https://github.com/johnkerl/miller.git
synced 2026-01-23 10:15:36 +00:00
508 lines
24 KiB
HTML
508 lines
24 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
|
|
<!-- PAGE GENERATED FROM template.html and content-for-build.html BY poki. -->
|
|
<!-- PLEASE MAKE CHANGES THERE AND THEN RE-RUN poki. -->
|
|
<head>
|
|
<meta http-equiv="Content-type" content="text/html;charset=UTF-8"/>
|
|
<meta name="description" content="Miller documentation"/>
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0"/> <!-- mobile-friendly -->
|
|
<meta name="keywords"
|
|
content="John Kerl, Kerl, Miller, miller, mlr, OLAP, data analysis software, regression, correlation, variance, data tools, " />
|
|
|
|
<title> Installation </title>
|
|
<link rel="stylesheet" type="text/css" href="css/miller.css"/>
|
|
<link rel="stylesheet" type="text/css" href="css/poki-callbacks.css"/>
|
|
</head>
|
|
|
|
<!-- ================================================================ -->
|
|
<script type="text/javascript">
|
|
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
|
|
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
|
|
</script>
|
|
<script type="text/javascript">
|
|
try {
|
|
var pageTracker = _gat._getTracker("UA-15651652-1");
|
|
pageTracker._trackPageview();
|
|
} catch(err) {}
|
|
</script>
|
|
<!-- ================================================================ -->
|
|
|
|
<body bgcolor="#ffffff">
|
|
|
|
<!-- ================================================================ -->
|
|
|
|
<!-- navbar -->
|
|
<div class="pokinav">
|
|
<center><titleinbody>Miller</titleinbody></center>
|
|
|
|
<!-- NAVBAR GENERATED FROM template.html BY poki -->
|
|
<br/>
|
|
<a class="poki-navbar-element" href="index.html">Overview</a>
|
|
|
|
<a class="poki-navbar-element" href="faq.html">Using</a>
|
|
|
|
<a class="poki-navbar-element" href="reference.html"><b>Reference</b></a>
|
|
|
|
<a class="poki-navbar-element" href="why.html">Background</a>
|
|
|
|
<a class="poki-navbar-element" href="contact.html">Repository</a>
|
|
|
|
<br/>
|
|
<br/><a href="reference.html">Main reference</a>
|
|
<br/><a href="reference-verbs.html">Verbs reference</a>
|
|
<br/><a href="reference-dsl.html">DSL reference</a>
|
|
<br/><a href="manpage.html">Manpage</a>
|
|
<br/><a href="release-docs.html">Documents by release</a>
|
|
<br/><a href="build.html"><b>Installation</b></a>
|
|
</div>
|
|
|
|
<!-- page body -->
|
|
<p/>
|
|
|
|
<!-- BODY COPIED FROM content-for-build.html BY poki -->
|
|
<div class="pokitoc">
|
|
<center><titleinbody>Installation</titleinbody></center>
|
|
• <a href="#Miller_license">Miller license</a><br/>
|
|
• <a href="#Prebuilt_executables">Prebuilt executables</a><br/>
|
|
• <a href="#Via_package_managers">Via package managers</a><br/>
|
|
• <a href="#Via_GitHub_per_release">Via GitHub per release</a><br/>
|
|
• <a href="#Building_from_source">Building from source</a><br/>
|
|
• <a href="#From_release_tarball_using_autoconfig">From release tarball using autoconfig</a><br/>
|
|
• <a href="#From_git_clone_using_autoconfig">From git clone using autoconfig</a><br/>
|
|
• <a href="#Without_using_autoconfig">Without using autoconfig</a><br/>
|
|
• <a href="#Windows">Windows</a><br/>
|
|
• <a href="#In_case_of_problems">In case of problems</a><br/>
|
|
• <a href="#Dependencies">Dependencies</a><br/>
|
|
• <a href="#Required_external_dependencies">Required external dependencies</a><br/>
|
|
• <a href="#Optional_external_dependencies">Optional external dependencies</a><br/>
|
|
• <a href="#Internal_dependencies">Internal dependencies</a><br/>
|
|
• <a href="#Creating_a_new_release:_for_developers">Creating a new release: for developers</a><br/>
|
|
• <a href="#Misc._development_notes">Misc. development notes</a><br/>
|
|
</div>
|
|
<p/>
|
|
|
|
<p/>
|
|
<button style="font-weight:bold;color:maroon;border:0" onclick="bodyToggler.expandAll();" href="javascript:;">Expand all sections</button>
|
|
<button style="font-weight:bold;color:maroon;border:0" onclick="bodyToggler.collapseAll();" href="javascript:;">Collapse all sections</button>
|
|
|
|
<a id="Miller_license"/><h1>Miller license</h1>
|
|
<button style="font-weight:bold;color:maroon;border:0" padding=0 onclick="bodyToggler.toggle('body_section_toggle_miller_license');" href="javascript:;">Toggle section visibility</button>
|
|
<div id="body_section_toggle_miller_license" style="display: block">
|
|
|
|
<p/>Two-clause BSD license <a href="https://github.com/johnkerl/miller/blob/master/LICENSE.txt">
|
|
https://github.com/johnkerl/miller/blob/master/LICENSE.txt</a>.
|
|
|
|
</div>
|
|
<a id="Prebuilt_executables"/><h1>Prebuilt executables</h1>
|
|
<button style="font-weight:bold;color:maroon;border:0" padding=0 onclick="bodyToggler.toggle('body_section_toggle_prebuilt_executables');" href="javascript:;">Toggle section visibility</button>
|
|
<div id="body_section_toggle_prebuilt_executables" style="display: block">
|
|
|
|
<a id="Via_package_managers"/><h2>Via package managers</h2>
|
|
|
|
<p/> Homebrew installation support for OSX is available via
|
|
|
|
<p/>
|
|
<div class="pokipanel">
|
|
<pre>
|
|
brew update && brew install miller
|
|
</pre>
|
|
</div>
|
|
<p/>
|
|
|
|
<p/>...and also via MacPorts:
|
|
|
|
<p/>
|
|
<div class="pokipanel">
|
|
<pre>
|
|
sudo port selfupdate && sudo port install miller
|
|
</pre>
|
|
</div>
|
|
<p/>
|
|
|
|
<p/> You may already have the <code>mlr</code> executable available in your platform’s
|
|
package manager on NetBSD, Debian Linux, Ubuntu Xenial and upward, Arch Linux, or perhaps other distributions.
|
|
For example, on various Linux distributions you might do one of the following:
|
|
|
|
<p/>
|
|
<div class="pokipanel">
|
|
<pre>
|
|
sudo apt-get install miller
|
|
</pre>
|
|
</div>
|
|
<p/>
|
|
<p/>
|
|
<div class="pokipanel">
|
|
<pre>
|
|
sudo apt install miller
|
|
</pre>
|
|
</div>
|
|
<p/>
|
|
<p/>
|
|
<div class="pokipanel">
|
|
<pre>
|
|
sudo yum install miller
|
|
</pre>
|
|
</div>
|
|
<p/>
|
|
|
|
<a id="Via_GitHub_per_release"/><h2>Via GitHub per release</h2>
|
|
|
|
<p/> Please see <a href="https://github.com/johnkerl/miller/releases">
|
|
https://github.com/johnkerl/miller/releases</a> where there are builds for OSX
|
|
Yosemite, Linux x86-64 (dynamically linked), and Windows (via Appveyor build artifacts).
|
|
|
|
<p/>Miller is autobuilt for <b>Linux</b> using <b>Travis</b> on every commit (<a
|
|
href="https://travis-ci.org/johnkerl/miller/builds">https://travis-ci.org/johnkerl/miller/builds</a>).
|
|
This was set up by the generous assistance of <a
|
|
href="https://github.com/SikhNerd">SikhNerd</a> on Github, tracked in <a
|
|
href="https://github.com/johnkerl/miller/issues/15">https://github.com/johnkerl/miller/issues/15</a>.
|
|
Analogously, Miller is autobuilt for <b>Windows</b> using the <b>Appveyor</b> continuous-build system:
|
|
<a href="https://ci.appveyor.com/project/johnkerl/miller">https://ci.appveyor.com/project/johnkerl/miller</a>.
|
|
|
|
<p/>Miller releases from <a
|
|
href="https://github.com/johnkerl/miller/releases/tag/v5.1.0w">5.1.0w</a>
|
|
onward will have a precompiled Windows binary, in addition to the MacOSX and
|
|
Linux 64-bit precompiled binaries as on previous releases. Specifically, at <a
|
|
href="https://ci.appveyor.com/project/johnkerl/miller">
|
|
https://ci.appveyor.com/project/johnkerl/miller</a> you can select <i>Latest
|
|
Build</i> and then <i>Artifacts</i> to always get the current head build.
|
|
Miller releases from 5.3.0 onward will simply point to a particular Appveyor
|
|
artifact associated with the release.
|
|
|
|
</div>
|
|
<a id="Building_from_source"/><h1>Building from source</h1>
|
|
<button style="font-weight:bold;color:maroon;border:0" padding=0 onclick="bodyToggler.toggle('body_section_toggle_building_from_source');" href="javascript:;">Toggle section visibility</button>
|
|
<div id="body_section_toggle_building_from_source" style="display: block">
|
|
|
|
<a id="From_release_tarball_using_autoconfig"/><h2>From release tarball using autoconfig</h2>
|
|
|
|
<p/>Miller allows you the option of using GNU <code>autoconfigure</code> to build portably.
|
|
|
|
<p/>Grateful acknowledgement: Miller’s GNU autoconfig work was done by
|
|
the generous and expert efforts of <a href="https://github.com/0-wiz-0/">Thomas
|
|
Klausner</a>.
|
|
|
|
<ul>
|
|
<li/> Obtain <code>mlr-i.j.k.tar.gz</code> from <a
|
|
href="https://github.com/johnkerl/miller/tags">https://github.com/johnkerl/miller/tags</a>,
|
|
replacing <code>i.j.k</code> with the desired release, e.g. <code>2.2.1</code>.
|
|
<li/> <code>tar zxvf mlr-i.j.k.tar.gz</code>
|
|
<li/> <code>cd mlr-i.j.k</code>
|
|
<li/> Install the following packages using your system’s package manager
|
|
(<code>apt-get</code>, <code>yum install</code>, etc.):
|
|
<b>flex</b>
|
|
<li> Various configuration options of your choice, e.g.
|
|
<ul>
|
|
<li/> <code>./configure</code>
|
|
<li/> <code>./configure --prefix=/usr/local</code>
|
|
<li/> <code>./configure --prefix=$HOME/pkgs</code>
|
|
<li/> <code>./configure CC=clang</code>
|
|
<li/> <code>./configure --disable-shared</code> (to make a statically linked executable)
|
|
<li/> <code>./configure 'CFLAGS=-Wall -std=gnu99 -O3'</code>
|
|
<li/> etc.
|
|
</ul>
|
|
<li/> <code>make</code> creates the <code>c/mlr</code> executable
|
|
<li/> <code>make check</code>
|
|
<li/> <code>make install</code> copies the <code>c/mlr</code> executable to your prefix’s <code>bin</code> subdirectory.
|
|
</ul>
|
|
|
|
<a id="From_git_clone_using_autoconfig"/><h2>From git clone using autoconfig</h2>
|
|
|
|
<ul>
|
|
<li/> <code>git clone https://github.com/johnkerl/miller</code>
|
|
<li/> <code>cd miller</code>
|
|
<li/> Install the following packages using your system’s package manager
|
|
(<code>apt-get</code>, <code>yum install</code>, etc.):
|
|
<b>automake autoconf libtool flex</b>
|
|
<li/> Run <code>autoreconf -fiv</code>. (This is necessary when building from head as discussed in
|
|
<a href="https://github.com/johnkerl/miller/issues/131">https://github.com/johnkerl/miller/issues/131</a>.)
|
|
<li/> Then continue from “Install the following ... ” as above.
|
|
</ul>
|
|
|
|
<a id="Without_using_autoconfig"/><h2>Without using autoconfig</h2>
|
|
|
|
<p/> GNU autoconfig is familiar to many users, and indeed plenty of folks won’t bother to use an open-source
|
|
software package which doesn’t have autoconfig support. And this is for good reason: GNU autoconfig allows
|
|
us to build software on a wide diversity of platforms. For this reason I’m happy that Miller supports
|
|
autoconfig.
|
|
|
|
<p/>But, many others (myself included!) find autoconfig confusing: if it works
|
|
without errors, great, but if not, the <code>./configure && make</code>
|
|
output can be exceedingly difficult to decipher. And this also can be a
|
|
turn-off for using open-source software: if you can’t figure out the
|
|
build errors, you may just keep walking. For this reason I’m happy that
|
|
Miller allows you to build without autoconfig. (Of course, if you have any
|
|
build errors, feel free to contact me at
|
|
<a href="mailto:kerl.john.r+miller@gmail.com">kerl.john.r+miller@gmail.com</a>,
|
|
— or, better, open an issue with “New Issue” at
|
|
<a href="https://github.com/johnkerl/miller/issues">
|
|
https://github.com/johnkerl/miller/issues</a>.)
|
|
|
|
<p/>Steps:
|
|
<ul>
|
|
<li/> Obtain a release tarball or git clone.
|
|
<li/> <code>cd</code> into the <code>c</code> subdirectory.
|
|
<li/> Edit the <code>INSTALLDIR</code> in <code>Makefile.no-autoconfig</code>.
|
|
<li/> To change the C compiler, edit the <code>CC=</code> lines in
|
|
<code>Makefile.no-autoconfig</code> and <code>dsls/Makefile.no-autoconfig</code>.
|
|
<li/> <code>make -f Makefile.no-autoconfig</code> creates the <code>mlr</code>
|
|
executable and runs unit/regression tests (i.e. the equivalent of both
|
|
<code>make</code> and <code>make check</code> using autoconfig).
|
|
<li/> <code>make install</code> copies the <code>mlr</code> executable to your install directory.
|
|
</ul>
|
|
|
|
<p/>The <code>Makefile.no-autoconfig</code> is simple: little more than <code>gcc
|
|
*.c</code>. Customzing is less automatic than autoconfig, but more transparent.
|
|
I expect this makefile to work with few modifications on a large fraction of
|
|
modern Linux/BSD-like systems: I’m aware of successful use with
|
|
<code>gcc</code> and <code>clang</code>, on Ubuntu 12.04 LTS, SELinux, Darwin (MacOS
|
|
Yosemite), and FreeBSD.
|
|
|
|
</div>
|
|
<a id="Windows"/><h2>Windows</h2>
|
|
|
|
<p/><i>Disclaimer: I’m now relying exclusively on
|
|
<a href="https://ci.appveyor.com/project/johnkerl/miller">Appveyor</a> for Windows
|
|
builds; I haven’t built from source using MSYS in quite a while.</i>
|
|
|
|
<p/>Miller has been built on Windows using MSYS2: <a
|
|
href="http://www.msys2.org/">http://www.msys2.org/</a>. You can install MSYS2
|
|
and build Miller from its source code within MSYS2, and then you can use the
|
|
binary from outside MSYS2. You can also use a precompiled binary (see above).
|
|
|
|
<p/> You will first need to install MSYS2: <a href="http://www.msys2.org/">http://www.msys2.org/</a>.
|
|
Then, start an MSYS2 shell, e.g. (supposing you installed MSYS2 to
|
|
<code>C:\msys2\</code>) run <code>C:\msys2\mingw64.exe</code>. Within the MSYS2 shell,
|
|
you can run the following to install dependent packages:
|
|
|
|
<div class=pokipanel>
|
|
<pre>
|
|
pacman -Syu
|
|
pacman -Su
|
|
pacman -S base-devel
|
|
pacman -S msys2-devel
|
|
pacman -S mingw-w64-x86_64-toolchain
|
|
pacman -S mingw-w64-x86_64-pcre
|
|
pacman -S msys2-runtime
|
|
</pre>
|
|
</div>
|
|
|
|
<p/>The list of dependent packages may be also found in <b>appveyor.yml</b>
|
|
in the Miller base directory.
|
|
|
|
<p/>Then, simply run <b>msys2-build.sh</b> which is a thin wrapper around
|
|
<code>./configure && make</code> which accommodates certain Windows/MSYS2
|
|
idiosyncracies.
|
|
|
|
<p/> There is a unit-test false-negative issue involving the semantics of the
|
|
<code>mkstemp</code> library routine but a <code>make -k</code> in the <code>c</code>
|
|
subdirectory has been producing a <code>mlr.exe</code> for me.
|
|
|
|
<p/> Within MSYS2 you can run <code>mlr</code>: simply copy it from the <code>c</code>
|
|
subdirectory to your desired location somewhere within your MSYS2
|
|
<code>$PATH</code>. To run <code>mlr</code> outside of MSYS2, just as with precompiled
|
|
binaries as described above, you’ll need <code>msys-2.0.dll</code>. One way
|
|
to do this is to augment your path:
|
|
|
|
<div class=pokipanel>
|
|
<pre>
|
|
C:\> set PATH=%PATH%;\msys64\mingw64\bin
|
|
</pre>
|
|
</div>
|
|
|
|
<p/> Another way to do it is to copy the Miller executable and the DLL to the same directory:
|
|
|
|
<div class=pokipanel>
|
|
<pre>
|
|
C:\> mkdir \mbin
|
|
C:\> copy \msys64\mingw64\bin\msys-2.0.dll \mbin
|
|
C:\> copy \msys64\wherever\you\installed\miller\c\mlr.exe \mbin
|
|
C:\> set PATH=%PATH%;\mbin
|
|
</pre>
|
|
</div>
|
|
|
|
</div>
|
|
<a id="In_case_of_problems"/><h1>In case of problems</h1>
|
|
<button style="font-weight:bold;color:maroon;border:0" padding=0 onclick="bodyToggler.toggle('body_section_toggle_in_case_of_problems');" href="javascript:;">Toggle section visibility</button>
|
|
<div id="body_section_toggle_in_case_of_problems" style="display: block">
|
|
|
|
<p/> If you have any build errors, feel free to contact me at <a
|
|
href="mailto:kerl.john.r+miller@gmail.com">kerl.john.r+miller@gmail.com</a>,
|
|
— or, better, open an issue with “New Issue” at
|
|
<a href="https://github.com/johnkerl/miller/issues">
|
|
https://github.com/johnkerl/miller/issues</a>.
|
|
|
|
</div>
|
|
<a id="Dependencies"/><h1>Dependencies</h1>
|
|
<button style="font-weight:bold;color:maroon;border:0" padding=0 onclick="bodyToggler.toggle('body_section_toggle_dependencies');" href="javascript:;">Toggle section visibility</button>
|
|
<div id="body_section_toggle_dependencies" style="display: block">
|
|
|
|
<a id="Required_external_dependencies"/><h2>Required external dependencies</h2>
|
|
|
|
<p/> These are necessary to produce the <code>mlr</code>
|
|
executable.
|
|
<ul>
|
|
<li/> <code>gcc</code>, <code>clang</code>, etc. (or presumably other compilers; please
|
|
open an issue or send me a pull request if you have information for me about
|
|
other 21st-century compilers)
|
|
<li/> The standard C library
|
|
<li/> <code>flex</code>
|
|
<li/> <code>automake</code>, <code>autoconf</code>, and <code>libtool</code>, if you build with autoconfig
|
|
</ul>
|
|
|
|
<a id="Optional_external_dependencies"/><h2>Optional external dependencies</h2>
|
|
|
|
This documentation pageset is built using <span class="boldmaroon">Poki</span>:
|
|
<a href="http://johnkerl.org/poki/doc">docs here</a>,
|
|
<a href="https://github.com/johnkerl/poki">source code here</a>.
|
|
Note that <a href="http://johnkerl.org/miller/doc/index.html">http://johnkerl.org/miller/doc/index.html</a>
|
|
is nothing more than Miller’s <code>doc</code> directory served up by a web server.
|
|
You’ll need <code>poki</code> if you modify documents, or if you modify the code in a way that affects the documents
|
|
(there are auto-run snippets inserted into the doc).
|
|
The best way to discover this is to run <code>make install</code> as above, then run <code>poki</code> in Miller’s
|
|
<code>doc</code> subdirectory, then run <code>git diff</code> to see if docs were affected
|
|
by the code mod. (If so, commit and push them.)
|
|
|
|
<a id="Internal_dependencies"/><h2>Internal dependencies</h2>
|
|
These are included within the <a href="https://github.com/johnkerl/miller">Miller source tree</a> and do not
|
|
need to be separately installed (and in fact any separate installation will not be picked up in the Miller build):
|
|
<ul>
|
|
<li/><a href="http://en.wikipedia.org/wiki/Mersenne_Twister">Mersenne Twister</a> for pseudorandom-number
|
|
generation: <a href="https://github.com/johnkerl/miller/blob/master/c/lib/mtrand.c">C implementation by Nishimura and Matsumoto</a> with license terms respected.
|
|
<li/> <a href="http://www.jera.com/techinfo/jtns/jtn002.html">MinUnit</a> for unit-testing,
|
|
with as-is-no-warranty license <a href="http://www.jera.com/techinfo/jtns/jtn002.html#License">http://www.jera.com/techinfo/jtns/jtn002.html#License</a>,
|
|
<a href="https://github.com/johnkerl/miller/blob/master/c/lib/minunit.h">
|
|
https://github.com/johnkerl/miller/blob/master/c/lib/minunit.h</a>.
|
|
<li/> The <a href="http://www.hwaci.com/sw/lemon/">Lemon parser-generator</a>, the author of which
|
|
<a href="https://github.com/johnkerl/miller/blob/master/c/dsls/lemon.c">explicitly disclaims
|
|
copyright</a>.
|
|
<li/> The <a href="https://github.com/udp/json-parser">udp JSON parser</a>, with BSD2 license.
|
|
<li/> The <a href="https://github.com/sheredom/utf8.h">sheredom UTF-8 library</a>, which is free and unencumbered software released into the public domain.
|
|
<li/> The NetBSD <code>strptime</code> (needed for the Windows/MSYS2 port since MSYS2 lacks this), with BSD license.
|
|
</ul>
|
|
|
|
</div>
|
|
<a id="Creating_a_new_release:_for_developers"/><h1>Creating a new release: for developers</h1>
|
|
<button style="font-weight:bold;color:maroon;border:0" padding=0 onclick="bodyToggler.toggle('body_section_toggle_creating_a_new_release');" href="javascript:;">Toggle section visibility</button>
|
|
<div id="body_section_toggle_creating_a_new_release" style="display: block">
|
|
|
|
<p/>At present I’m the primary developer so this is just my checklist for making new releases.
|
|
|
|
<p/>In this example I am using version 3.4.0; of course that will change for subsequent revisions.
|
|
<ul>
|
|
|
|
<li>Update version found in <code>mlr --version</code> and <code>man mlr</code>:
|
|
<ul>
|
|
<li/> Edit <code>configure.ac</code>, <code>c/mlrvers.h</code>, and <code>miller.spec</code>
|
|
from <code>3.3.2-dev</code> to <code>3.4.0</code>.
|
|
<li/> Do a fresh <code>autoreconf -fiv</code> and commit the output.
|
|
<li/> <code>make -C c -f Makefile.no-autoconfig installhome &&
|
|
make -C doc -f Makefile.no-autoconfig all installhome</code>
|
|
<li/> Commit and push.
|
|
<li/> ISP upload so <a href="http://johnkerl.org/miller/doc/index.html">http://johnkerl.org/miller/doc/index.html</a>
|
|
will have updated head-docs.
|
|
</ul>
|
|
|
|
<li>Create the release tarball and SRPM:
|
|
<ul>
|
|
<li/> On buildbox: <code>./configure && make distcheck</code>
|
|
<li/> On buildbox: make SRPM as in <a href="https://github.com/johnkerl/miller/blob/master/README-RPM.md">
|
|
https://github.com/johnkerl/miller/blob/master/README-RPM.md</a>
|
|
<li/> On all buildboxes: <code>cd c</code> and <code>make -f Makefile.no-autoconfig mlr.static</code>. Then copy
|
|
<code>mlr.static</code> to <code>../mlr.{arch}</code>. (This may require as prerequisite <code>sudo yum install glibc-static</code> or the like.)
|
|
<ul>
|
|
<li>For static binaries, please do <code>ldd mlr.static</code> and make sure it says <code>not a dynamic executable</code>.</li>
|
|
<li>Then <code>mv mlr.static ../mlr.linux_x86_65</code>
|
|
</ul>
|
|
<li/> Pull back release tarball <code>mlr-3.4.0.tar.gz</code> and SRPM <code>mlr-3.4.0-1.el6.src.rpm</code> from buildbox,
|
|
and <code>mlr.{arch}</code> binaries from whatever buildboxes.
|
|
<li/> Download <code>mlr.exe</code> and <code>msys-2.0.dll</code> from
|
|
<a href="https://ci.appveyor.com/project/johnkerl/miller/build/artifacts">https://ci.appveyor.com/project/johnkerl/miller/build/artifacts</a>.
|
|
</ul>
|
|
|
|
<li/>Create the Github release tag:
|
|
<ul>
|
|
<li/> Don’t forget the <code>v</code> in <code>v3.4.0</code>
|
|
<li/> Write the release notes
|
|
<li/> Attach the release tarball, SRPM, and binaries. Double-check assets were successfully uploaded.
|
|
<li/> Publish the release
|
|
</ul>
|
|
|
|
<li/>Create the release-specific docs:
|
|
<ul>
|
|
<li/> Pull the Github-generated source <code>.tgz</code> from Github to ISP
|
|
miller-releases directory and unpack and <code>cd</code> into it.
|
|
<li/> <code>cd</code> into <code>doc</code> subdir. Edit <code>template.html</code>’s <code>titleinbody</code> tag from
|
|
<code>Miller</code> to <code>Miller 3.4.0</code> and poki-build.
|
|
<li/> ISP upload
|
|
<li/> At the ISP site, update the latest-revision symlink
|
|
<code>ln -s pub_http_internet/miller-releases/miller-3.4.0 pub_http_internet/miller</code>.
|
|
(This is the main doc URL linked to from the top of the Github repo so it
|
|
must point to this newly published revision.)
|
|
<li/> Back in the Github repo, edit <code>doc/content-for-release-docs.html</code> to include new release, poki-build,
|
|
push/commit, and ISP upload.
|
|
</ul>
|
|
|
|
<li/>Notify:
|
|
<ul>
|
|
<li/> Submit <code>brew</code> pull request; notify any other distros which don’t appear to have autoupdated
|
|
since the previous release.
|
|
<pre>
|
|
git remote add upstream https://github.com/Homebrew/homebrew-core # one-time setup only
|
|
git fetch upstream
|
|
git rebase upstream/master
|
|
git checkout -b miller-3.4.0
|
|
shasum -a 256 /path/to/mlr-3.4.0.tar.gz
|
|
edit Formula/miller.rb
|
|
# Test the URL from the line like
|
|
# url "https://github.com/johnkerl/miller/releases/download/v3.4.0/mlr-3.4.0.tar.gz"
|
|
# in a browser for typos
|
|
# A '@BrewTestBot Test this please' comment within the homebrew-core pull request will restart the homebrew travis build
|
|
git add Formula/miller.rb
|
|
git commit -m 'miller 3.4.0'
|
|
git push -u origin miller-3.4.0
|
|
(submit the pull request)
|
|
</pre>
|
|
<li/> Similarly for <tt>macports</tt>: <a href="https://github.com/macports/macports-ports/blob/master/textproc/miller/Portfile">https://github.com/macports/macports-ports/blob/master/textproc/miller/Portfile</a>.
|
|
<li/> Update
|
|
<a href="https://github.com/johnkerl/miller/issues/163">https://github.com/johnkerl/miller/issues/163</a>
|
|
(release-tracker issue).
|
|
<li/> Social-media updates.
|
|
</ul>
|
|
|
|
<li/>Afterwork:
|
|
<ul>
|
|
<li> Edit <code>configure.ac</code> and <code>c/mlrvers.h</code> to change version from <code>3.4.0</code> to
|
|
<code>3.4.0-dev</code>.
|
|
<li/> <code>make -C c -f Makefile.no-autoconfig installhome &&
|
|
make -C doc -f Makefile.no-autoconfig all installhome</code>
|
|
<li> Commit and push.
|
|
</ul>
|
|
|
|
</ul>
|
|
|
|
</div>
|
|
<a id="Misc._development_notes"/><h1>Misc. development notes</h1>
|
|
<button style="font-weight:bold;color:maroon;border:0" padding=0 onclick="bodyToggler.toggle('body_section_toggle_misc_devel_notes');" href="javascript:;">Toggle section visibility</button>
|
|
<div id="body_section_toggle_misc_devel_notes" style="display: block">
|
|
|
|
<p/>I use terminal width 120 and tabwidth 4.
|
|
|
|
</div>
|
|
|
|
<!-- ================================================================ -->
|
|
<script type="text/javascript" src="js/miller-doc-toggler.js"></script>
|
|
<!-- wtf -->
|
|
<script type="text/javascript">
|
|
// Put this at the bottom of the page since its constructor scans the
|
|
// document's div tags to find the toggleables.
|
|
const bodyToggler = new MillerDocToggler(
|
|
"body_section_toggle_",
|
|
'maroon',
|
|
'maroon',
|
|
);
|
|
</script>
|
|
|
|
</body>
|
|
</html>
|