User:Colby Russell/Non-uniform build scripts: Difference between revisions
From triplescripts.org wiki
Content added Content deleted
(Created page with "The linking page says: <blockquote>still intended to be dropped into a repo and vendored like script modules, but the bundle will be an agglomeration of modules likely to be maintained independently of the project and upgraded all-at-once</blockquote> As of this writing, the majority of the (small set) of triple scripts are using unmodified copies of trplkt as their Build.app.htm. This raises the possibility of more custom build scripts—e.g. ones that co...") |
(s/build/builder/) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
The [[linking]] page says: |
The [[linking]] page says: |
||
<blockquote>still intended to be dropped into a repo and vendored like script modules, but the bundle will be an agglomeration of modules likely to be maintained independently of the project and upgraded all-at-once</blockquote> |
<blockquote>pre-compiled bundles that are still intended to be dropped into a repo and vendored like script modules, but the bundle will be an agglomeration of modules likely to be maintained independently of the project and upgraded all-at-once</blockquote> |
||
As of this writing, the majority of the (small set) of triple scripts are using unmodified copies of trplkt as their [[Build.app.htm]]. This raises the possibility of more custom build scripts—e.g. ones that consist only of a custom shunting block that links against a trplkt-derived libpack and a project-specific build coordination module. |
As of this writing, the majority of the (small set) of triple scripts are using unmodified copies of trplkt as their [[Build.app.htm]]. This raises the possibility of more custom build scripts—e.g. ones that consist only of a custom shunting block that links against a trplkt-derived libpack and a project-specific build coordination module. XXX A convention to consider: <code>meta/builder/</code> as the appropriate place in the source tree. |
||
Latest revision as of 16:58, 12 March 2023
The linking page says:
pre-compiled bundles that are still intended to be dropped into a repo and vendored like script modules, but the bundle will be an agglomeration of modules likely to be maintained independently of the project and upgraded all-at-once
As of this writing, the majority of the (small set) of triple scripts are using unmodified copies of trplkt as their Build.app.htm. This raises the possibility of more custom build scripts—e.g. ones that consist only of a custom shunting block that links against a trplkt-derived libpack and a project-specific build coordination module. XXX A convention to consider: meta/builder/ as the appropriate place in the source tree.