Contributed Code
Overview
Antelope provides a productive development environment for end-users to create specialized processing applications.
Occasionally, members of the Antelope User Community release libraries and programs they’ve developed for broad use. These contributions are quite valuable to the Antelope community.
Both source-code and compiled versions of these contributed programs are available from web-sites maintained by the Antelope User Community (not by BRTT). The contributed programs may be installed alongside Antelope, to work in conjunction with the official Antelope release. Downloading the contributed code requires acceptance of the license terms placed on the software components by each contributing author.
During Antelope installation, the Antelope installer will offer users the opportunity to make this separate download of the contributed softare provided they agree to the contributed-code licensing terms. Alternatively, Antelope ships with a script install_contrib(1) which allows users to download and install the contributed software from Antelope User Community web-sites after Antelope is already installed.
For more information on Antelope contributed software, see the man-page contrib(5).
BRTT DISCLAIMS ALL OWNERSHIP, LIABILITY, AND SUPPORT FOR CONTRIBUTED SOFTWARE NOT WRITTEN BY BRTT.
BRTT makes no claims of ownership for any of the contributed software other than the software BRTT itself has contributed. BRTT disclaims any responsibility relating to the contributed software. Any use of the contributed-code software, including redistribution, should first be cleared with the original authors, if such terms are not already explicit in the LICENSE included with the software element in question.
Contributed code: NO BRTT supportor the following notation at the bottom of the man page for the program:
Antelope Contrib SW
- As an option during the Antelope installation process;
- At a later time via the supplied install_contrib(1) script;
- Downloading and installing the compiled tarball by hand; or
- By compiling the contributed source-code oneself.
Itemized Steps — option A (Antelope installer option)
The default option to install the contributed code is to approve download and unpacking of the contributed-code tarball when prompted by the main Antelope installation program. This method requires a working internet connection that can connect to the appropriate web-site to download the contributed-code tarball:- Install Antelope
- During the Antelope installation process, respond “Yes” when prompted by the installer to “Download contributed code?” (one of the last steps in the installation process)
Itemized Steps — option B (install_contrib(1) script)
If you choose not to install the contributed code during the Antelope installation process, or you do not have an internet connection at the time, you may install later via the install_contrib(1) script. This option also requires an internet connection:- source the appropriate setup file ($ANTELOPE/setup.csh or $ANTELOPE/setup.sh)
- Run the program install_contrib
Itemized Steps — option C (download and install by hand)
In lieu of running the install_contrib(1) script, you may download and install the relevant files by hand:- Check the current download location and filename:
% pfecho install_antelope 'contribcode_params{download_site}' 'contribcode_params{filename}' contribcode_params{download_site} https://github.com/antelopeusersgroup/antelope_contrib/releases/download/5.9 contribcode_params{filename} Darwin_x86_contrib.tar.bz2
- Download the file with web-browser, wget or similar utility:
% wget 'https://github.com/antelopeusersgroup/antelope_contrib/releases/download/5.10/Darwin_x86_contrib.tar.bz2'
(Note that the URL will change depending on the platform you’re on) - Install the contributed-code file:
% mv Darwin_x86_contrib.tar.bz2 /opt/antelope % cd /opt/antelope % bunzip2 -c Darwin_x86_contrib.tar.bz2 | tar xvf -
Itemized Steps — option D (compile from source)
If you wish, you may download the contributed-code source and compile it yourself:-
- Make sure Antelope is installed
- source the appropriate setup file $ANTELOPE/setup.csh or $ANTELOPE/setup.sh
- In a terminal window or shell, run the following:
- % cd $ANTELOPE
- % mkdir contrib
- % cd contrib
- % git clone https://github.com/antelopeusersgroup/antelope_contrib src
- % cd src
- % make Include
- % make install
Requests for support should be made to the original authors, who should be identified in the man-page. None of the contributed software libraries and programs are constrained by Antelope licensing. Source code for the contributed software modules may be obtained via the Antelope Users Group web site.
BRTT leaves the management and contents of the contributed code repository as much as possible to the user community, with the one exception that we will occasionally submit programs of possible interest.
BRTT recommends contributed-code software adhere to a few simple guidelines. These are just suggestions; BRTT will not police what our users do:
- We suggest each utility have a man-page with author/affiliation, name, and synopsis (usage line) specified
- We suggest each utility have a Makefile compatible with ANTELOPEMAKE, as described by the man-page antelopemakefile(5)
- We suggest each utility have an explicit license, saved in a file called LICENSE in the source-code directory, so other users know what is OK for them to do with the code, and presumably one that allows the Antelope User Community to use and distribute it.
There are many available open-source licenses, not all of which are created equal. Some examples of licenses that work well include: