| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\
| |
| |
| |
| | |
Update NEWS
See merge request BuildStream/buildstream!1579
|
|/
|
|
| |
[ci skip]
|
|\
| |
| |
| |
| | |
Update requirements for 1.4
See merge request BuildStream/buildstream!1578
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
| |
Some dependencies need wheel to be installed before their installation
is started as it provides extra setup.py commands.
|
|\
| |
| |
| |
| | |
Prepare 1.4.0
See merge request BuildStream/buildstream!1575
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
Support strict build dependencies (bst 1)
See merge request BuildStream/buildstream!1574
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is in order to keep the door open to allowing the project.conf
set the default of dependency 'strict'-ness which might be useful
for projects which use mostly static linking and the like, in which
case we can later interpret explicitly non-strict dependencies
as an override of the project default.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This tests that the target which depends on a common dependency
strictly in non strict mode needs to be rebuilt after this common
dependency changes, while it is not the case when depending on the
same common target non strictly.
This is a regression test for #254
|
| | |
|
| |
| |
| |
| |
| |
| | |
This adds documentation on the new keyword `strict` in dependency
declarations, and adds a link to the strict mode user config
section.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch allows specifying a dependency as `strict`, e.g.:
build-depends:
- filename: element.bst
strict: true
This allows finer tuning of projects which want to leverage
the non-strict build mode; dependencies which are statically
linked to, or who's content is otherwise included verbatim in
the resulting output, should be marked `strict` to ensure these
bits get reassembled if necessary when building in non-strict
mode.
This fixes #254
Change summary:
o _loader/types.pyx: Added 'strict' attribute to Dependency
and do the parsing work.
o _loader/metaelement.py: Added 'strict_dependencies' list
o _loader/loader.py: Resolve the 'strict_dependencies' list
o element.py: Added __strict_dependencies list, and use this
to conditionally use weak cache keys in place of names for
the purpose of building the weak cache key (in the case of
dependencies which are marked as strict).
|
|/
|
|
|
|
|
|
| |
As discussed with Jürg on gitlab[0], it makes more sense to store the
recursive element names and record the shape of the dependencies for
non strict cache keys as well as strict ones.
[0]: https://gitlab.com/BuildStream/buildstream/merge_requests/1542#note_205598556
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 08ead05bbe24a6de94e26b1121e5aa8dd341f691.
This commit was introduced to fix #1097, however it appears to not
be needed anymore after e48a03b2b226f1748edf5c2d5e28093da7ca6a1a which
uses a newer version of bst-external.
However, moving to fedora-30 runtime DID introduce a regression with
the ostree plugin, causing out-of-sync error messages to consistently
occur whenever fetching an ostree source.
Reverting to the old debian 9 docker image appears to fix the
ostree installation to work, fixing the afore mentioned regression
outlined in issue #1098.
This fixes #1098.
|
| |
|
|
|
|
| |
[ci skip]
|
|
|
|
| |
This reverts commit 7f73c0dd2eae616a719d2bee68135f96a0df52bd.
|
| |
|
|
|
|
| |
Fixes #1097
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Backport some misc fixes (bst-1)
See merge request BuildStream/buildstream!1517
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes the configurable warning part of this to properly link
to the project.conf documentation describing what configurable
warnings actually are.
Also fix the plugin raise the actual configurable warning which
it advertizes that it raises; which is 'inconsistent-submodule',
not 'inconsistent-submodules'.
|
| |
| |
| |
| |
| |
| |
| | |
Now the commands have documentation linkability so we can link to
them when referring to them anywhere in the docs. This reference
was previously referring to a bogus non-existent `build-stream track`,
maybe this dates way back to the days before we named the frontend `bst`.
|
| |
| |
| |
| |
| |
| | |
This also ensures it is exposed via the main buildstream __init__.py
file, fixes the imports of CoreWarnings, and adjusts the documentation
links to point to the right place.
|
|/
|
|
|
| |
Instead of duplicating the whole test body, run it twice while
checking for a warning or an error depending on the parameter.
|
|\
| |
| |
| |
| | |
Backport relative workspaces (bst-1)
See merge request BuildStream/buildstream!1519
|
|/
|
|
|
|
|
| |
This fixes #191
A note has been added to NEWS explaining backwards
compatibility issues
|
|\
| |
| |
| |
| | |
Backport json cache keys (bst-1)
See merge request BuildStream/buildstream!1518
|
| | |
|
|/
|
|
|
|
|
|
| |
This affects the cache key version (updated to 7) and introduces
a dependency on `ujson` which is BSD licenced as of the version
locked in `requirements.txt`
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
|\
| |
| |
| |
| | |
Backport pretty git refs
See merge request BuildStream/buildstream!1516
|
| | |
|
| | |
|
|/
|
|
| |
Use `git describe` to prefix `ref` with closest tag, if available.
|
|\
| |
| |
| |
| | |
Backport git submodule warnings
See merge request BuildStream/buildstream!1515
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
o Test that it is not triggered in show before fetch, because we
don't know the submodules yet so we cannot know if they are
valid or not.
o Test that it is triggered by a fetch command
o Test that it is triggered by `show` after having completed a
fetch command, since now we have the repository and know which
specified submodules are invalid
o Test all of this under warning or error conditions (parameterized
for fatal-warnings)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
o Test that it is not triggered in show before fetch, because we
don't know about the unlisted submodules yet
o Test that it is triggered by a fetch command
o Test that it is triggered by `show` after having completed a
fetch command, since now we have the repository and know about
the unlisted submodule
o Test all of this under warning or error conditions (parameterized
for fatal-warnings)
|
| |
| |
| |
| |
| | |
A function for removing paths from a git repo, can also
be used to remove submodules.
|