indirect

managing package manager package lists, for easier installs

What it does

Helps with managing lists of indirect objects, i.e. packages. Outputs scripts for installing with various package managers. Transforms the data into csv format, a step towards improved handling with dative or other tools.

Motivation

Pretty much every platform or programming language has a package manager. I got tired of forgetting what packages I use, why, and how they install. So I started making lists such as these. This tool parses the text files and generates data for further scripting. By default, it produces install scripts. Installing is my main motivation.

Install

A Makefile installs indirect to /usr/local, which is configurable...

From source, using git and make:

git clone https://github.com/orlin/indirect.git # or your own fork of it
cd indirect
make install

Or, with bpkg:

curl -sLo- http://get.bpkg.io | bash # in case you don't already have it
bpkg install -g orlin/indirect

Use

indirect --help

Last I tried, says:

Usage: indirect [-d] [-p] file(s)

  <file(s)> can be globs / paths:
  relative to a configured $INDIRECT_PACKAGES location or
  a packages symbolic link in your installation directory.
  Or else, one can use any paths with the --path option...

  -d, --data     Get CSV data rather than installation scripts
  -p, --path     Provide real paths, skip convenient shortcuts
  -h, --help     Display this help

  For more information, see https://github.com/orlin/indirect

Configuration

$INDIRECT_PACKAGES by default your package lists are expected to be relative to this env variable path or to a packages directory symlinked into indirect.sh's directory, there is an option to use direct paths though
$INDIRECT_HOME it's possible to set your indirect.sh's directory - which was added for testing purposes, and should not be needed otherwise

Test

Testing needs npm, i.e. node.js installed.

npm i -g batshit #once
npm test

License

MIT