Skip to content

Latest commit

 

History

History
69 lines (48 loc) · 2.43 KB

README.md

File metadata and controls

69 lines (48 loc) · 2.43 KB
Raw

archutil

Release MIT License

Please see the upstream project for the original README.

Description

This fork has been updated for Python 3, and modified to use a yaml configuration file: archutil.yml. The configuration management functions have been removed.

The location of archutil.yml can be specified via the -c flag. By default, archutil will look for this file in the following order:

  1. In the current working directory.
  2. In /usr/local/etc.

Addtional changes include a new --sets flags and better AUR support.

Installation

Only bin/archutil is required. This can be installed manually to /usr/local/bin.

You will also need the python and python-yaml packages.

For convenience, the latest version of archutil is provided at https://io.evansosenko.com/archutil/archutil and a package.json is included for use with npm or yarn.

For fetching and installing during initial setup, you can use

$ [sudo] curl -L -o /usr/local/bin/archutil https://git.io/jgz3
$ [sudo] chmod +x /usr/local/bin/archutil

Contributing

Please submit and comment on bug reports and feature requests.

To submit a patch:

  1. Fork it (https://github.com/rxrc/vimrc/fork).
  2. Create your feature branch (git checkout -b my-new-feature).
  3. Make changes.
  4. Commit your changes (git commit -am 'Add some feature').
  5. Push to the branch (git push origin my-new-feature).
  6. Create a new Pull Request.

License

archutil is licensed under the MIT license.

Warranty

This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright holder or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.