| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This simplifies the loading
|
|
|
|
|
|
| |
This removes the need for the 'Dependency' list to then be matched
with the corresponding LoadElement and will allow iterating the
graph more easily
|
|
|
|
|
| |
Now that 'bst fetch' is obsolete, change guidance to refer to the
replacement 'bst source fetch' instead.
|
|
|
|
|
| |
Now that 'bst track' is obsolete, change guidance to refer to the
replacement 'bst source track' instead.
|
|
|
|
|
| |
See https://mail.gnome.org/archives/buildstream-list/2018-December/msg00061.html
for some related discussion.
|
|
|
|
|
|
|
| |
Currently we some duplication in the way we check for invalid filenames.
To make it more robust and allow room for adding more warnings, refactor
it into a separate method `_warn_invalid_elements()` that handles just
this.
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
_loader/loader.py: Added Suffix check and warning for named elements and add helper function
|
|
|
|
|
| |
This eliminates unneeded copies of the project directory for junctions
with a single local source.
|
| |
|
|
|
|
|
|
|
|
| |
Since python 3.3, collections has been moved to collections.abc module.
For backwards compatibility, they continue to be visible in this module through Python 3.7.
Subsequently, they will be removed entirely.
See https://docs.python.org/3/library/collections.html
|
|
|
|
|
|
|
|
|
| |
When a circular dependency is detected, the reported error hilights
only one part of the loop in question. This change ensures that
the entire loop is listed so that the user has a greater chance of
easily determining the correct fix.
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
|
|
|
|
|
| |
Note that the ProvenanceFile's names will be incorrect after loading
from the cache, but this is currently only used for writeback, which
isn't used in junctions.
|
| |
|
|
|
|
|
|
|
|
|
| |
Issue was introduced by 171e803f (include directive) and the fix was
found courtesy of @Qinusty. This fixes also the include
feature. Because elements are to be serialized, the included fragments
need to use copy_tree when loaded.
Related to #470.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Source plugin implementations can now specify that they need access to
previously staged sources by specifying
`BST_REQUIRES_PREVIOUS_SOURCES_TRACK` and/or
`BST_REQUIRES_PREVIOUS_SOURCES_FETCH`, corresponding to access at `track`
and `fetch` times respectively.
Fixes #381.
Replaces !505. For relevant discussion, see this discussion:
https://gitlab.com/BuildStream/buildstream/merge_requests/505#note_83780747
|
|
|
|
| |
Fixes #331.
|
| |
|
|
|
|
|
| |
This is required to be able to build a Loader before the list
of targets is known.
|
|
|
|
|
|
|
|
|
|
|
| |
**KLUDGE WARNING**: This involves making the source store its "meta"
object so that it's possible to create a copy of the source inside the
fetch queue, instead of back when the pipeline was being loaded.
This adds the SourceFetcher class, which is intended for sources that
fetch from multiple URLs (e.g. the git source and its submodules)
Fix when fetching
|
|
|
|
|
| |
- Slight modification to the wording of existing error message.
- Closes #446
|
|
|
|
| |
Fixes #424
|
|
|
|
|
|
| |
'a.bst:b.bst' gets interpreted as 'b.bst' from junction 'a.bst'.
Part of #359.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It can be confusing, especially to new BuildStream users, that the CLI
expects targets to be specified relative to element-path and not the
current directory. Previously, the CLI would give a generic message
stating that the file could not be found but it was not obvious that it
was looking in the `element-path` directory.
Explicitly print the element-path in the summary. Also, try to check if
the specified element exists in the elements directory and print a hint
to use the element-path relative paths if that's the case.
Fixes #396.
This is is also related to #341. This commit aims to tackle that issue
by trying to educate users about element-path.
|
|
|
|
|
|
|
|
|
| |
This was previously decided in CLI, but knowledge of what to initialize
has been moved to Stream().
Now there is no more point to store this configuration in the Context,
we just have the Stream() decide it when asking the Pipeline() to
invoke the Loader().
|
|
|
|
|
|
| |
Leave this error to be handled by preflight.
Updated test case to expect the new ElementError instead of a LoadError
|
|
|
|
|
|
| |
This is needed so that Sources can derive whether they belong
to a junction or not, which is needed for separating where
junction refs are stored.
|
| |
|
|
|
|
|
|
| |
This is actually used by the Loader and is not private.
This is a part of #285
|
|
|
|
|
|
|
| |
This also refactors the loader code to honor private symbol
naming policy.
This is a part of issue #285
|
|
|