<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/buildstream.git/src/buildstream/_loader/loadelement.pyx, branch bschubert/cleanups</title>
<subtitle>gitlab.com: buildstream/buildstream.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/'/>
<entry>
<title>_loader: Adding LoadContext</title>
<updated>2020-06-16T16:18:21+00:00</updated>
<author>
<name>Tristan van Berkom</name>
<email>tristan.vanberkom@codethink.co.uk</email>
</author>
<published>2020-06-14T12:23:19+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=deb6562719c2ca90b5fbdc2974e8a77da8430a96'/>
<id>deb6562719c2ca90b5fbdc2974e8a77da8430a96</id>
<content type='text'>
Instead of passing around many details though calling signatures
throughout the loader code, create a single LoadContext object
which holds any overall loading state along with any values which
are constant to a full load process.

Overall this patch does:

  * _frontend/app.py: No need to pass Stream.fetch_subprojects() along anymore

  * _loader/loadelement.pyx: collect_element_no_deps() no longer takes a task argument

  * _loader/loader.py: Now the Loader has a `load_context` member, and no more
    `_fetch_subprojects` member or `_context` members

    Further, `rewritable` and `ticker` is no longer passed along through all
    of the recursing calling signatures, and `ticker` itself is finally removed
    because this has been replaced a long time ago with `Task` API from `State`.

  * _pipeline.py: The load() function no longer has a `rewritable` parameter

  * _project.py: The Project() is responsible for creating the toplevel
    LoadContext() if one doesn't exist yet, and this is passed through
    to the Loader() (and also passed to the Project() constructor by the
    Loader() when instantiating subprojects).

  * _stream.py: The `Stream._fetch_subprojects()` is now private and set
    on the project when giving the Project to the Stream in `Stream.set_project()`,
    also the Stream() sets the `rewritable` state on the `LoadContext` at the
    earliest opportunity, as the `Stream()` is the one who decides this detail.

    Further, some double underscore private functions are now regular single
    underscores, there was no reason for this inconsistency.

  * tests/internals/loader.py: Updated for API change
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Instead of passing around many details though calling signatures
throughout the loader code, create a single LoadContext object
which holds any overall loading state along with any values which
are constant to a full load process.

Overall this patch does:

  * _frontend/app.py: No need to pass Stream.fetch_subprojects() along anymore

  * _loader/loadelement.pyx: collect_element_no_deps() no longer takes a task argument

  * _loader/loader.py: Now the Loader has a `load_context` member, and no more
    `_fetch_subprojects` member or `_context` members

    Further, `rewritable` and `ticker` is no longer passed along through all
    of the recursing calling signatures, and `ticker` itself is finally removed
    because this has been replaced a long time ago with `Task` API from `State`.

  * _pipeline.py: The load() function no longer has a `rewritable` parameter

  * _project.py: The Project() is responsible for creating the toplevel
    LoadContext() if one doesn't exist yet, and this is passed through
    to the Loader() (and also passed to the Project() constructor by the
    Loader() when instantiating subprojects).

  * _stream.py: The `Stream._fetch_subprojects()` is now private and set
    on the project when giving the Project to the Stream in `Stream.set_project()`,
    also the Stream() sets the `rewritable` state on the `LoadContext` at the
    earliest opportunity, as the `Stream()` is the one who decides this detail.

    Further, some double underscore private functions are now regular single
    underscores, there was no reason for this inconsistency.

  * tests/internals/loader.py: Updated for API change
</pre>
</div>
</content>
</entry>
<entry>
<title>_loader/loadelement.pyx: Load full element names recursively.</title>
<updated>2020-06-08T14:50:34+00:00</updated>
<author>
<name>Tristan Van Berkom</name>
<email>tristan.vanberkom@codethink.co.uk</email>
</author>
<published>2020-05-06T10:47:11+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=c9a00fd7124810b38b1343dda4265444c29d603b'/>
<id>c9a00fd7124810b38b1343dda4265444c29d603b</id>
<content type='text'>
When opening up the possibility of loading the same junction twice,
it becomes possible to have multiple elements with the same name
following the current implementation logic which enforces that
you must have a toplevel junction to coalesce junctions and synchronize
their configuration.

Since we no longer coalesce junction names, we need to allow elements
to be reported in the UI with their full depth.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When opening up the possibility of loading the same junction twice,
it becomes possible to have multiple elements with the same name
following the current implementation logic which enforces that
you must have a toplevel junction to coalesce junctions and synchronize
their configuration.

Since we no longer coalesce junction names, we need to allow elements
to be reported in the UI with their full depth.
</pre>
</div>
</content>
</entry>
<entry>
<title>link element: Adding support for new link element</title>
<updated>2020-06-01T14:11:04+00:00</updated>
<author>
<name>Tristan van Berkom</name>
<email>tristan.vanberkom@codethink.co.uk</email>
</author>
<published>2020-05-30T10:37:44+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=f774efaa72f3400ff8bd506a0fd7c536fd8f608f'/>
<id>f774efaa72f3400ff8bd506a0fd7c536fd8f608f</id>
<content type='text'>
This element acts as a symbolic link, it has no other configurations
other than to specify the element (or junction) to which it refers to,
either in the local project or in a subproject.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This element acts as a symbolic link, it has no other configurations
other than to specify the element (or junction) to which it refers to,
either in the local project or in a subproject.
</pre>
</div>
</content>
</entry>
<entry>
<title>loader.py: Optimize sorting of elements when they are multiple targets</title>
<updated>2020-01-14T16:52:09+00:00</updated>
<author>
<name>Benjamin Schubert</name>
<email>bschubert15@bloomberg.net</email>
</author>
<published>2020-01-14T14:54:35+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=0b75e62fe83bd1a6af3e73ef3a53c5bf475e35d9'/>
<id>0b75e62fe83bd1a6af3e73ef3a53c5bf475e35d9</id>
<content type='text'>
Currently, with multiple targets, we would go through all the elements
in the target and sort them, even though they might already be sorted.

This ensures we sort every element only once.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Currently, with multiple targets, we would go through all the elements
in the target and sort them, even though they might already be sorted.

This ensures we sort every element only once.
</pre>
</div>
</content>
</entry>
<entry>
<title>Implement strict dependency semantics</title>
<updated>2019-08-31T12:05:52+00:00</updated>
<author>
<name>Tristan Van Berkom</name>
<email>tristan.vanberkom@codethink.co.uk</email>
</author>
<published>2019-08-12T19:33:53+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=cc51e4a2d4f338b4dd49337432170b4e30ebe8d0'/>
<id>cc51e4a2d4f338b4dd49337432170b4e30ebe8d0</id>
<content type='text'>
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/loadelement.pyx: Added 'strict' attribute to Dependency

  o _loader/types.pyx: Added 'strict' attribute to Dependency
    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).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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/loadelement.pyx: Added 'strict' attribute to Dependency

  o _loader/types.pyx: Added 'strict' attribute to Dependency
    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).
</pre>
</div>
</content>
</entry>
<entry>
<title>loader: Move sort_dependencies to loadelement as a cython method</title>
<updated>2019-07-26T07:55:26+00:00</updated>
<author>
<name>Benjamin Schubert</name>
<email>ben.c.schubert@gmail.com</email>
</author>
<published>2019-07-22T16:12:18+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=862e9c3f60b46b7f80a223dbff0b95cf5423a197'/>
<id>862e9c3f60b46b7f80a223dbff0b95cf5423a197</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>loadelement: Move loadelement to Cython</title>
<updated>2019-07-26T07:55:26+00:00</updated>
<author>
<name>Benjamin Schubert</name>
<email>ben.c.schubert@gmail.com</email>
</author>
<published>2019-07-22T14:17:42+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/buildstream.git/commit/?id=fada80df076fc1ccf3991a3f9344c68a1db8bcda'/>
<id>fada80df076fc1ccf3991a3f9344c68a1db8bcda</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
