Update config-available for clpBNR v0.12.0 #180
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add clpBNR_toolkit and clpBNR to preload on SWISH (now req'd for sanboxing).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add
clpBNR_toolkitandclpBNR_searchto preload on SWISH (now req'd for sandboxing). This should be done as part of any SWISH build incorporating theclpBNRv0.12.0.clpBNRv0.12.0 includes:a) new module
clpBNR_searchwhich is a version of ECLIPSe search libraries(e.g.,fd_search) forclpBNRon SWI-Prolog.b) additional predicates in module
clpBNR_toolkitsupporting numerical integration.Both modules require the addition of sandboxing rules which, I think, dictates that they must be pre-loaded on SWISH. (clpBNR_toolkit could be used previously without preloading because no
sandboxpredicates were required.)I've tested the above on a local SWISH server but can retest on a non-production server is desired.
A "process" question: The version of
clpBNR(v0.11.7b) currently running on SWISH is several releases old. Is there something I need to do on producing a new version ofclpBNRto trigger its inclusion in the next SWISH build? Or can something be done to the SWISH "make" scripts, e.g.,pack_upgrade(clpBNR)so this happens automatically? If so will this also include the appropriate copy of the clpBNR quickstart notebook from the Git repo to examples?Off topic question: Getting the version of available packs on SWISH is a bit problematical because
pack-info(and related) are sandboxed on SWISH. I've added clpBNR version to the version info (using the documented hook) but maybe something from the pack manager could be white-listed so this wouldn't be necessary.