Lines Matching +full:- +full:- +full:github

10 libxo source code lives on github:
12   https://github.com/Juniper/libxo
16   https://github.com/Juniper/libxo/releases
25   git clone https://github.com/Juniper/libxo.git -b develop
29     http://nvie.com/posts/a-successful-git-branching-model
32 our github site.
35 -----------------------------
39 A. Use a "distfile" for a specific release.  We use github to maintain
42    green "Latest release" button and the green "libxo-RELEASE.tar.gz"
45 .. _release page: https://github.com/Juniper/libxo/releases
49        tar -zxf libxo-RELEASE.tar.gz
50        cd libxo-RELEASE
54      Note: for Solaris users, your "`tar`" command lacks the "-z" flag,
55      so you'll need to substitute "`gzip -dc $file | tar xf -`" instead
56      of "`tar -zxf $file`".
58 B. Use the current build from github.  This gives you the most recent
62        git clone https://github.com/Juniper/libxo.git
67      The github repository does **not** contain the files generated by
69      Since these files (depcomp, configure, missing, install-sh, etc) are
81 --------------
121 environment. Use "`configure --help`" to view these options.
139 By default, libxo installs architecture-independent files, including
142 include the --prefix=prefix option and specify an alternate
144 user-defined location, include the "*--with-extensions-dir=dir*" option
181 Verify the installation by viewing the output of "`xo --version`"::
183     % xo --version
184     libxo version 0.3.5-git-develop
185     xo version 0.3.5-git-develop