Reusability: Difference between revisions
no edit summary
(grammar + "expected") |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
Line 1:
Programs implemented as triple scripts are expected to vendor their dependencies. In other words, maintainers should distribute third-party code in the same source tree as the project's own code. If using version control (e.g. Git), the third-party modules (i.e. the ''content'' of those modules—not pointers to their entry on some external package repository) are expected to be checked in to version control system. '''The triplescripts.org group's approach to publishing is not compatible with the package.json convention from the NPM ecosystem''' (or indeed many of the other traditions in the NodeJS world).
For programs which are not implemented as triple scripts but *do* adhere to the [[build manifesto]] (i.e. they use a triple script-based build system), program dependencies MUST be either vendored as well OR provide some means of obtaining ALL third-party code necessary to build the program in a single-shot (preferably with a single HTTP <code>GET</code> request to a user-visible URL).
Line 12:
NB: Even though the triple script approach does not work in terms of semver pointers, programmers ARE encouraged to continue using semantic versioning—it's just that the triple script approach eschews operating on pointers in lieu of direct use of the module contents.
There is no tooling at this time for actually managing
== See also ==
| |||