- 26 Apr, 2020 1 commit
-
-
Julien Muchembled authored
-
- 23 Apr, 2020 4 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
Julien Muchembled authored
-
Jérome Perrin authored
-
- 22 Apr, 2020 5 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
Julien Muchembled authored
It is redundant with the fact that slapos.buildout already rebuilds if any dependency is modified. slapos.buildout does not yet understand the new => syntax from upstream buildout but meanwhile a dummy option can be set to any options of required parts.
-
Julien Muchembled authored
The value was always '${:_profile_base_location_}'
-
Julien Muchembled authored
In conjunction with the new Options.barrier() in buildout, parts will be able to modify the environment during install/update.
-
- 15 Apr, 2020 1 commit
-
-
Julien Muchembled authored
-
- 31 Mar, 2020 1 commit
-
-
Jérome Perrin authored
-
- 30 Mar, 2020 1 commit
-
-
Dmitry Blinov authored
If not set, the commands in the middle of custom configure-command, pre-build, post-build etc can fail without resulting in SystemError for user and without stopping cmmi process, which thus can formally succeed despite being misconfigured or in some cases with the code not even built. This is because when executing a multiline command, only the exit status of the last one actually gets caught by check_call(). Setting -e makes debugging easier by allowing shell to terminate mid-way if errors (non-zero exit status) occur. -e only covers 'simple commands', and does not affect 'if' tests and more complex cases where non-zero exit status is expected to occur normally. Detailed description of -e effects can be seen in the POSIX standard: https://pubs.opengroup.org/onlinepubs/009695399/utilities/set.html
-
- 12 Dec, 2019 1 commit
-
-
Jérome Perrin authored
-
- 10 Dec, 2019 1 commit
-
-
Jérome Perrin authored
When build process is interrupted (like when the buildout process terminated by SIGKILL), building with shared leave the system in a state that looks like installation succeeded, so next execution will assume the part was properly installed. The behavior was something like this: if isSharedPartSignatureOK(): useThisAlreadyInstalledPart() else: writeSignatureInSharedPart() try: build() except: removeSharedPart() raise and when program is terminated during build step, the signature is there. The fix is to write signature later, algorithm becomes: if isSharedPartSignatureOK(): useThisAlreadyInstalledPart() else: try: build() except: removeSharedPart() raise writeSignatureInSharedPart() /reviewed-on nexedi/slapos.recipe.cmmi!10
-
- 05 Dec, 2019 1 commit
-
-
Jérome Perrin authored
-
- 02 Oct, 2019 4 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
Use a new option `buildout:shared-path-list` that is now a new line separated list of path, only the last part is used to install new parts, other are read-only. Also some cleanups in the test suite. /reviewed-on nexedi/slapos.recipe.cmmi!9
-
- 01 Oct, 2019 1 commit
-
-
Jérome Perrin authored
on python3.6, subprocess error message is different, use a zope.testing.renormalizing rule to normalize the message.
-
- 30 Sep, 2019 1 commit
-
-
Jérome Perrin authored
This will allow nested slapos where the inner slapos can re-use shared parts from outer slapos, but not write into the outer shared parts. For compatibility reasons, the syntax of the buildout option changed, instead of the old ${buildout:shared-parts} that use to be one path, we now use ${buildout:shared-part-list} as a \n separated list of paths. All paths can be used to lookup existing parts, only the last one can be used to install new parts. There is no compatibility with the old option as it was not used much, only in profiles which were not really compatible with shared options.
-
- 26 Sep, 2019 3 commits
-
-
Jérome Perrin authored
https://pypi.org/project/zope.testing/ features "renormalizing" that this test was already using to make this test independent from actual paths that can be different but use some paths that looks always the same (like /sample_buildout/). Also use this in our patches for shared support so that the test is a bit more readable and also so that we can assert the actual hash being used.
-
Jérome Perrin authored
-
Jérome Perrin authored
-
- 25 Sep, 2019 1 commit
-
-
Jérome Perrin authored
This is restructured text.
-
- 30 Nov, 2018 3 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
Julien Muchembled authored
This is not the default with Python 2.
-
- 29 Oct, 2018 2 commits
-
-
Julien Muchembled authored
-
Bryton Lacquement authored
-
- 16 Oct, 2018 2 commits
-
-
Jérome Perrin authored
This reverts daa833ea ( nexedi/slapos.recipe.cmmi!3 ) and extend it to not set `$TMP` either. De facto, setting only `$TMP` was never effective ( see also [#20120530-132221B](https://nexedi.erp5.net/bug_module/20120530-132221B) ) and as we saw in nexedi/slapos.recipe.cmmi!3 (comment 67059) it causes more harm than good. The conclusion so far is that environment variables related to temporary files should be handled by the parent process. The parent process is responsible for providing a directory short enough so that we can create unix sockets in `$TMPDIR` and to clean up this directory afterwards. In a pure buildout it could be: ```bash tmpdir=$(mktemp -d) trap 'rm -rf $tmpdir' SIGINT SIGTERM TEMP=$tmpdir TMPDIR=$tmpdir TMP=$tmpdir buildout rm -rf $tmpdir ``` /reviewed-on nexedi/slapos.recipe.cmmi!8
-
Jérome Perrin authored
It was inconsistent to only set TMP and not TEMP / TEMPDIR. In the case of slapos, it should be set by slapos node software Most installation seem to cleanup tmp properly, so the use case cleaning up seem not critical. This TMP was also used to know what new files have been created, by considering files newer that the creation date of this directory. Compare the file dates with the creation of the source directory instead ( xxx__compile__ )
-
- 04 Oct, 2018 1 commit
-
-
Nicolas Wavrant authored
-
- 02 Oct, 2018 2 commits
-
-
Jérome Perrin authored
This reverts commit daa833ea.
-
Jérome Perrin authored
To make it easyier to diagnose build errors. /reviewed-on nexedi/slapos.recipe.cmmi!7
-
- 19 Sep, 2018 1 commit
-
-
Jérome Perrin authored
We were already setting $TMP, but many software uses $TMPDIR or $TEMP.
-
- 18 Sep, 2018 1 commit
-
-
Jérome Perrin authored
-
- 27 Aug, 2018 2 commits
-
-
Yusei Tahara authored
-
Yusei Tahara authored
Fix a doctest failure. Since shared part is read-only, it is necessary to change permission before removing.
-