Skip to content

Commit

Permalink
Bump spec to v1.10, better describe find_regexp
Browse files Browse the repository at this point in the history
Part of KSP-CKAN#1089.
  • Loading branch information
pjf committed Jun 28, 2015
1 parent e7cd4f9 commit ffbbab8
Showing 1 changed file with 9 additions and 5 deletions.
14 changes: 9 additions & 5 deletions Spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ reference CKAN client that will read this file.
For compatibility with pre-release clients, and the v1.0 client, the special
*integer* `1` should be used.

This document describes the CKAN specification 'v1.8'. Changes since spec `1`
This document describes the CKAN specification 'v1.10'. Changes since spec `1`
are marked with **v1.2** through to **v1.8** respectively. For maximum
compatibility, using older spec versions is preferred when newer features are
not required.
Expand Down Expand Up @@ -245,8 +245,8 @@ ALPHA or pre-), or with silly orderings.

##### install

A list of install directives for this mod, each *must* contain one of
three mandatory source directives:
A list of install directives for this mod, each *must* contain exactly one of
three source directives:

- `file`: The file or directory root that this directive pertains to.
All leading directories are stripped from the start of the filename
Expand All @@ -256,10 +256,14 @@ three mandatory source directives:
the name specified. This is particularly useful when distributions
have structures which change based upon each release.
- `find_regexp`: (**v1.10**) Locate the top-most directory which matches
the specified regular expression. This is particular useful when
the specified regular expression. This is particularly useful when
distributions have structures which change based upon each release, but
`find` cannot be used because multiple directories or files contain the
same name.
same name. Directories separators will have been normalised to
forward-slashes first, and the trailing slash for each directory removed
before the regular expresssion is run.
*Use sparingly and with caution*, it's *very* easy to match the wrong
thing with a regular expression.

In addition a destination directive *must* be provided:

Expand Down

0 comments on commit ffbbab8

Please sign in to comment.