#57 Implement dependency check and document dependencies
Opened 6 years ago by tibbs. Modified 6 years ago

There needs to be a function run after the config is passed which checks for the presence of the necessary dependencies. Particularly for doing the checkin. The documentation also needs to be checked.

  • awk (Do we use gnu extensions?)
  • sed (Do we use gnu extensions?)
  • tr
  • rsync
  • bzip2 for checkins only
  • base64 for checkins only
  • curl for checkins only
  • sort
  • uniq
  • grep (egrep)
  • gnu grep required for test suite only (we use -P)

All of the above should be made configurable (rsync and curl are done already). This allows someone to override with gnu versions or whatnot. The test suite probably doesn't need to adapt to this, though. At least not initially.

Finally, the documentation needs to be updated with all of these dependencies.


Metadata Update from @tibbs:
- Issue set to the milestone: 0.1

6 years ago

Login to comment on this ticket.

Metadata