You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildstream.apache.org by tv...@apache.org on 2021/01/05 09:17:02 UTC
[buildstream] branch master updated (cd2f743 -> c02e5c1)
This is an automated email from the ASF dual-hosted git repository.
tvb pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/buildstream.git.
from cd2f743 Removing all traces of gitlab metadata
new 1000229 BuildStream.doap: Remove BuildStream.doap
new b8736e4 CONTRIBUTING.rst: Updating some references to gitlab
new 91c6dce COMMITTERS.rst: s/gitlab/github
new ccd03ee doc/source/arch_sandboxing.rst: s/gitlab/github
new 2440543 doc/source/additional_docker.rst: s/gitlab/github
new 044c917 doc/source/hacking/ui.rst: s/gitlab/github
new 24bfee7 doc/source/main_install.rst: s/gitlab/github
new c02e5c1 docs examples: s/gitlab/github
The 8 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
BuildStream.doap | 32 ------------
COMMITTERS.rst | 4 +-
CONTRIBUTING.rst | 75 ++++++++++------------------
doc/source/additional_docker.rst | 7 ++-
doc/source/arch_sandboxing.rst | 6 +--
doc/source/developing/strict-mode.rst | 2 +-
doc/source/developing/workspaces.rst | 2 +-
doc/source/examples/flatpak-autotools.rst | 4 +-
doc/source/hacking/ui.rst | 9 ++--
doc/source/handling-files/composition.rst | 2 +-
doc/source/handling-files/filtering.rst | 2 +-
doc/source/handling-files/overlaps.rst | 2 +-
doc/source/junctions/junction-elements.rst | 4 +-
doc/source/junctions/junction-includes.rst | 2 +-
doc/source/junctions/junction-workspaces.rst | 2 +-
doc/source/main_install.rst | 7 +--
doc/source/tutorial/autotools.rst | 2 +-
doc/source/tutorial/directives.rst | 2 +-
doc/source/tutorial/first-project.rst | 2 +-
doc/source/tutorial/integration-commands.rst | 4 +-
doc/source/tutorial/running-commands.rst | 2 +-
21 files changed, 59 insertions(+), 115 deletions(-)
delete mode 100644 BuildStream.doap
[buildstream] 08/08: docs examples: s/gitlab/github
Posted by tv...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tvb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/buildstream.git
commit c02e5c19e068b13a18ee72793f0d3747d880ce8d
Author: Tristan van Berkom <tr...@codethink.co.uk>
AuthorDate: Tue Jan 5 18:15:18 2021 +0900
docs examples: s/gitlab/github
---
doc/source/developing/strict-mode.rst | 2 +-
doc/source/developing/workspaces.rst | 2 +-
doc/source/examples/flatpak-autotools.rst | 4 ++--
doc/source/handling-files/composition.rst | 2 +-
doc/source/handling-files/filtering.rst | 2 +-
doc/source/handling-files/overlaps.rst | 2 +-
doc/source/junctions/junction-elements.rst | 4 ++--
doc/source/junctions/junction-includes.rst | 2 +-
doc/source/junctions/junction-workspaces.rst | 2 +-
doc/source/tutorial/autotools.rst | 2 +-
doc/source/tutorial/directives.rst | 2 +-
doc/source/tutorial/first-project.rst | 2 +-
doc/source/tutorial/integration-commands.rst | 4 ++--
doc/source/tutorial/running-commands.rst | 2 +-
14 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/doc/source/developing/strict-mode.rst b/doc/source/developing/strict-mode.rst
index a3ee231..e516a66 100644
--- a/doc/source/developing/strict-mode.rst
+++ b/doc/source/developing/strict-mode.rst
@@ -12,7 +12,7 @@ can help to improve your edit/compile/test cycles.
This example is distributed with BuildStream
in the `doc/examples/strict-mode
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/strict-mode>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/strict-mode>`_
subdirectory.
diff --git a/doc/source/developing/workspaces.rst b/doc/source/developing/workspaces.rst
index 2413c56..b9691d0 100644
--- a/doc/source/developing/workspaces.rst
+++ b/doc/source/developing/workspaces.rst
@@ -11,7 +11,7 @@ devloping a BuildStream project.
This example is distributed with BuildStream
in the `doc/examples/developing
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/developing>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/developing>`_
subdirectory.
We will start with the project used in the :ref:`running commands <tutorial_running_commands>`
diff --git a/doc/source/examples/flatpak-autotools.rst b/doc/source/examples/flatpak-autotools.rst
index bfafb2b..c8d9de1 100644
--- a/doc/source/examples/flatpak-autotools.rst
+++ b/doc/source/examples/flatpak-autotools.rst
@@ -10,7 +10,7 @@ a Flatpak SDK for the base runtime.
This example is distributed with BuildStream
in the `doc/examples/flatpak-autotools
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/flatpak-autotools>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/flatpak-autotools>`_
subdirectory.
@@ -123,7 +123,7 @@ just a few things you can try to do with the project.
The following examples assume that you have first changed your working
directory to the
- `project root <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/flatpak-autotools>`_.
+ `project root <https://github.com/apache/buildstream/tree/master/doc/examples/flatpak-autotools>`_.
Build the hello.bst element
diff --git a/doc/source/handling-files/composition.rst b/doc/source/handling-files/composition.rst
index 729ed88..2adfda3 100644
--- a/doc/source/handling-files/composition.rst
+++ b/doc/source/handling-files/composition.rst
@@ -11,7 +11,7 @@ input filesystem trees, using the :mod:`compose <elements.compose>` element.
This example is distributed with BuildStream
in the `doc/examples/composition
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/composition>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/composition>`_
subdirectory.
diff --git a/doc/source/handling-files/filtering.rst b/doc/source/handling-files/filtering.rst
index 27cdfe6..4fa3b4c 100644
--- a/doc/source/handling-files/filtering.rst
+++ b/doc/source/handling-files/filtering.rst
@@ -12,7 +12,7 @@ depend on a subset of the files provided by a filtered element.
This example is distributed with BuildStream
in the `doc/examples/filtering
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/filtering>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/filtering>`_
subdirectory.
diff --git a/doc/source/handling-files/overlaps.rst b/doc/source/handling-files/overlaps.rst
index 25456d2..ab573d9 100644
--- a/doc/source/handling-files/overlaps.rst
+++ b/doc/source/handling-files/overlaps.rst
@@ -12,7 +12,7 @@ use to resolve these situations.
This example is distributed with BuildStream
in the `doc/examples/overlaps
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/overlaps>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/overlaps>`_
subdirectory.
diff --git a/doc/source/junctions/junction-elements.rst b/doc/source/junctions/junction-elements.rst
index 8de3d53..fb95523 100644
--- a/doc/source/junctions/junction-elements.rst
+++ b/doc/source/junctions/junction-elements.rst
@@ -24,7 +24,7 @@ A simple example
.. note::
This example is distributed with BuildStream in the
- `doc/examples/junctions <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/junctions>`_
+ `doc/examples/junctions <https://github.com/apache/buildstream/tree/master/doc/examples/junctions>`_
subdirectory.
Below is a simple example of bst file for the junction element, which
@@ -34,7 +34,7 @@ we have called ``hello-junction.bst`` in this project:
:language: yaml
This element imports the autotools example subproject distributed with BuildStream
-in the `doc/examples/junctions/autotools <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/junctions/autotools>`_
+in the `doc/examples/junctions/autotools <https://github.com/apache/buildstream/tree/master/doc/examples/junctions/autotools>`_
subdirectory.
.. note::
diff --git a/doc/source/junctions/junction-includes.rst b/doc/source/junctions/junction-includes.rst
index 17de81b..b8d0e77 100644
--- a/doc/source/junctions/junction-includes.rst
+++ b/doc/source/junctions/junction-includes.rst
@@ -19,7 +19,7 @@ of your :mod:`junction <elements.junction>`.
This example is distributed with BuildStream
in the `doc/examples/junction-includes
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/junction-includes>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/junction-includes>`_
subdirectory.
diff --git a/doc/source/junctions/junction-workspaces.rst b/doc/source/junctions/junction-workspaces.rst
index a917606..82b73ad 100644
--- a/doc/source/junctions/junction-workspaces.rst
+++ b/doc/source/junctions/junction-workspaces.rst
@@ -16,7 +16,7 @@ in your own project.
This section runs commands on the same example project presented in the
:ref:`previous section <junction_elements>`, which is distributed with BuildStream in the
- `doc/examples/junctions <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/junctions>`_
+ `doc/examples/junctions <https://github.com/apache/buildstream/tree/master/doc/examples/junctions>`_
subdirectory.
diff --git a/doc/source/tutorial/autotools.rst b/doc/source/tutorial/autotools.rst
index c8fec3b..3e89688 100644
--- a/doc/source/tutorial/autotools.rst
+++ b/doc/source/tutorial/autotools.rst
@@ -18,7 +18,7 @@ on the :mod:`manual <elements.manual>` element, and observe how
This example is distributed with BuildStream
in the `doc/examples/autotools
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/autotools>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/autotools>`_
subdirectory.
diff --git a/doc/source/tutorial/directives.rst b/doc/source/tutorial/directives.rst
index a23b5f9..33d9eeb 100644
--- a/doc/source/tutorial/directives.rst
+++ b/doc/source/tutorial/directives.rst
@@ -13,7 +13,7 @@ YAML format.
This example is distributed with BuildStream
in the `doc/examples/directives
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/directives>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/directives>`_
subdirectory.
diff --git a/doc/source/tutorial/first-project.rst b/doc/source/tutorial/first-project.rst
index c83e740..ca3fd5b 100644
--- a/doc/source/tutorial/first-project.rst
+++ b/doc/source/tutorial/first-project.rst
@@ -11,7 +11,7 @@ could think of.
This example is distributed with BuildStream
in the `doc/examples/first-project
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/first-project>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/first-project>`_
subdirectory.
diff --git a/doc/source/tutorial/integration-commands.rst b/doc/source/tutorial/integration-commands.rst
index 558d3d5..8113ac6 100644
--- a/doc/source/tutorial/integration-commands.rst
+++ b/doc/source/tutorial/integration-commands.rst
@@ -19,7 +19,7 @@ ensure that a runtime is ready to run after all of its components have been *sta
This example is distributed with BuildStream
in the `doc/examples/integration-commands
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/integration-commands>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/integration-commands>`_
subdirectory.
@@ -77,7 +77,7 @@ seen in the previous chapter: :ref:`tutorial_running_commands`.
These produce a library and a hello program which uses the library,
we will consider these irrelevant to the topic and leave examination
of `their sources
-<https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/integration-commands/files>`_
+<https://github.com/apache/buildstream/tree/master/doc/examples/integration-commands/files>`_
as an exercise for the reader.
diff --git a/doc/source/tutorial/running-commands.rst b/doc/source/tutorial/running-commands.rst
index 1708145..586a621 100644
--- a/doc/source/tutorial/running-commands.rst
+++ b/doc/source/tutorial/running-commands.rst
@@ -12,7 +12,7 @@ the :ref:`isolated build sandbox <sandboxing>`.
This example is distributed with BuildStream
in the `doc/examples/running-commands
- <https://gitlab.com/BuildStream/buildstream/tree/master/doc/examples/running-commands>`_
+ <https://github.com/apache/buildstream/tree/master/doc/examples/running-commands>`_
subdirectory.
[buildstream] 01/08: BuildStream.doap: Remove BuildStream.doap
Posted by tv...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tvb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/buildstream.git
commit 10002291784f84fb308a6aaf0f758d6b8ada93c2
Author: Tristan van Berkom <tr...@codethink.co.uk>
AuthorDate: Tue Jan 5 17:42:11 2021 +0900
BuildStream.doap: Remove BuildStream.doap
This is a metadata file specific to gnome automations/integrations.
---
BuildStream.doap | 32 --------------------------------
1 file changed, 32 deletions(-)
diff --git a/BuildStream.doap b/BuildStream.doap
deleted file mode 100644
index 15894b2..0000000
--- a/BuildStream.doap
+++ /dev/null
@@ -1,32 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<Project xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
- xmlns:foaf="http://xmlns.com/foaf/0.1/"
- xmlns:gnome="http://api.gnome.org/doap-extensions#"
- xmlns="http://usefulinc.com/ns/doap#">
-
- <name xml:lang="en">BuildStream</name>
- <shortdesc xml:lang="en">Build tool for running abstract, deterministic build pipelines</shortdesc>
- <homepage rdf:resource="https://gitlab.com/BuildStream/buildstream/" />
- <mailing-list rdf:resource="https://lists.apache.org/list.html?dev@buildstream.apache.org" />
- <download-page rdf:resource="http://download.gnome.org/sources/BuildStream/" />
- <bug-database rdf:resource="https://gitlab.com/BuildStream/buildstream/issues" />
-
- <category rdf:resource="http://api.gnome.org/doap-extensions#apps" />
- <programming-language>python3</programming-language>
-
- <maintainer>
- <foaf:Person>
- <foaf:name>Tristan Van Berkom</foaf:name>
- <foaf:mbox rdf:resource="mailto:tristan.vanberkom@codethink.co.uk" />
- <gnome:userid>tvb</gnome:userid>
- </foaf:Person>
- </maintainer>
- <maintainer>
- <foaf:Person>
- <foaf:name>Jürg Billeter</foaf:name>
- <foaf:mbox rdf:resource="mailto:juerg.billeter@codethink.co.uk" />
- <gnome:userid>juergbi</gnome:userid>
- </foaf:Person>
- </maintainer>
-</Project>
[buildstream] 02/08: CONTRIBUTING.rst: Updating some references to
gitlab
Posted by tv...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tvb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/buildstream.git
commit b8736e43d66c56ce86010ae6b0f9af9c07554ea9
Author: Tristan van Berkom <tr...@codethink.co.uk>
AuthorDate: Tue Jan 5 17:56:31 2021 +0900
CONTRIBUTING.rst: Updating some references to gitlab
---
CONTRIBUTING.rst | 75 ++++++++++++++++++++------------------------------------
1 file changed, 26 insertions(+), 49 deletions(-)
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index b03388e..7d9e862 100644
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -8,8 +8,8 @@ Some tips and guidelines for developers hacking on BuildStream
Filing issues
-------------
If you are experiencing an issue with BuildStream, or would like to submit a patch
-to fix an issue, then you should first search the list of `open issues <https://gitlab.com/BuildStream/buildstream/issues>`_
-to see if the issue is already filed, and `open an issue <https://gitlab.com/BuildStream/buildstream/issues/new>`_
+to fix an issue, then you should first search the list of `open issues <https://github.com/apache/buildstream/issues>`_
+to see if the issue is already filed, and `open an issue <https://github.com/apache/buildstream/issues/new>`_
if no issue already exists.
@@ -52,23 +52,17 @@ process, giving us a reasonable timeframe for identifying these.
Submitting patches
------------------
-
-
-Ask for developer access
-~~~~~~~~~~~~~~~~~~~~~~~~
-If you want to submit a patch, do ask for developer permissions, either
-by asking us directly on our public IRC channel (irc://irc.gnome.org/#buildstream)
-or by visiting our `project page on GitLab <https://gitlab.com/BuildStream/buildstream>`_
-and using the GitLab UI to ask for permission.
-
-This will make your contribution experience smoother, as you will not
-need to setup any complicated CI settings, and rebasing your branch
-against the upstream master branch will be more painless.
+Submitting patches works in the regular GitHub workflow of submitting
+pull requests.
Branch names
~~~~~~~~~~~~
-Branch names for merge requests should be prefixed with the submitter's
+If you are an apache member with access to the main repository, and are
+submitting a pull request for a branch within the main repository, then
+please be careful to use an identifiable branch name.
+
+Branch names for pull requests should be prefixed with the submitter's
name or nickname, followed by a forward slash, and then a descriptive
name. e.g.::
@@ -79,36 +73,26 @@ belongs to whom, especially so that we can effectively cleanup stale
branches in the upstream repository over time.
-Merge requests
-~~~~~~~~~~~~~~
+Pull requests
+~~~~~~~~~~~~~
Once you have created a local branch, you can push it to the upstream
BuildStream repository using the command line::
- git push origin username/fix-that-bug:username/fix-that-bug
+ git push origin username/fix-that-bug
-GitLab will respond to this with a message and a link to allow you to create
-a new merge request. You can also `create a merge request for an existing branch
-<https://gitlab.com/BuildStream/buildstream/merge_requests/new>`_.
+GitHub will respond to this with a message and a link to allow you to create
+a new merge request. You can also `create a pull request using the GitHub UI
+<https://github.com/apache/buildstream/compare>`_.
-You may open merge requests for the branches you create before you are ready
+You may open pull requests for the branches you create before you are ready
to have them reviewed and considered for inclusion if you like. Until your merge
-request is ready for review, the merge request title must be prefixed with the
-``WIP:`` identifier. GitLab `treats this specially
-<https://docs.gitlab.com/ee/user/project/merge_requests/work_in_progress_merge_requests.html>`_,
-which helps reviewers.
+request is ready for review, the pull request title must be prefixed with the
+``WIP:`` identifier.
-Consider marking a merge request as WIP again if you are taking a while to
+Consider marking a pull request as WIP again if you are taking a while to
address a review point. This signals that the next action is on you, and it
won't appear in a reviewer's search for non-WIP merge requests to review.
-As a general rule of thumb, after a month of no activity from the submitter of
-a non-WIP MR, we'll put it back into WIP with a polite note. Then after another
-month with no activity we'll close the MR off entirely with another note.
-In this way we are trying to ensure all of the MRs in our backlog are relevant
-and up to date. We have some `boilerplate text
-<https://gitlab.com/BuildStream/buildstream/blob/master/.gitlab/merge_request_templates/stale_MR_message.md>`_,
-to help us when writing these notes.
-
Organized commits
@@ -135,9 +119,7 @@ with the same commit, so that every commit passes its own tests.
These principles apply whenever a branch is non-WIP. So for example, don't push
'fixup!' commits when addressing review comments, instead amend the commits
-directly before pushing. GitLab has `good support
-<https://docs.gitlab.com/ee/user/project/merge_requests/versions.html>`_ for
-diffing between pushes, so 'fixup!' commits are not necessary for reviewers.
+directly before pushing.
Commit messages
@@ -198,24 +180,18 @@ separately.
Committer access
----------------
-
Committers in the BuildStream project are those folks to whom the right to
directly commit changes to our version controlled resources has been granted.
-While every contribution is
-valued regardless of its source, not every person who contributes code to the
-project will earn commit access. The `COMMITTERS`_ file lists all committers.
-Whenever someone is granted (or revoked) commit access, an Owner or Maintainer
-should run the the script located at `contrib/update_committers.py` with their
-personal access token, updating the COMMITTERS.rst list and opening an MR
-with their changes.
+While every contribution is valued regardless of its source, not every person
+who contributes code to the project will earn commit access.
+The `COMMITTERS`_ file lists all committers.
-.. _COMMITTERS: https://gitlab.com/BuildStream/buildstream/blob/master/COMMITTERS.rst
+.. _COMMITTERS: https://github.com/apache/buildstream/blob/master/COMMITTERS.rst
How commit access is granted
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
After someone has successfully contributed a few non-trivial patches, some full
committer, usually whoever has reviewed and applied the most patches from that
contributor, proposes them for commit access. This proposal is sent only to the
@@ -244,9 +220,9 @@ project needs a bunch of very trivial patches whose only purpose is to gain comm
access; knowing what's worth a patch post and what's not is part of showing good
judgement.)
+
Windows CI
----------
-
The infrastructure for running the CI against Windows is different from the usual
runners, due to a combination of licensing technicalities and differing
containerisation support.
@@ -256,6 +232,7 @@ The scripts used to generate a CI runner can be found at
The `wsl` branch can be used to generate a runner for WSL, and the `win32` branch
can be used to generate a native-windows runner.
+
Further information
-------------------
[buildstream] 05/08: doc/source/additional_docker.rst:
s/gitlab/github
Posted by tv...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tvb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/buildstream.git
commit 24405438aa50f6b83b6e001d687f0b25f1fe0cdb
Author: Tristan van Berkom <tr...@codethink.co.uk>
AuthorDate: Tue Jan 5 18:04:13 2021 +0900
doc/source/additional_docker.rst: s/gitlab/github
---
doc/source/additional_docker.rst | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/doc/source/additional_docker.rst b/doc/source/additional_docker.rst
index 0cddad2..a7cfd28 100644
--- a/doc/source/additional_docker.rst
+++ b/doc/source/additional_docker.rst
@@ -16,8 +16,7 @@ documentation for instructions on how to run BuildStream as a Docker container.
Generate Docker images
----------------------
-The
-`bst-docker-import script <https://gitlab.com/BuildStream/buildstream/blob/master/contrib/bst-docker-import>`_
+The `bst-docker-import script <https://github.com/apache/buildstream/blob/master/contrib/bst-docker-import>`_
can be used to generate a Docker image from built artifacts.
You can download it and make it executable like this:
@@ -25,7 +24,7 @@ You can download it and make it executable like this:
.. code:: bash
mkdir -p ~/.local/bin
- curl --get https://gitlab.com/BuildStream/buildstream/raw/master/contrib/bst-docker-import > ~/.local/bin/bst-docker-import
+ curl --get https://raw.githubusercontent.com/apache/buildstream/master/contrib/bst-docker-import > ~/.local/bin/bst-docker-import
chmod +x ~/.local/bin/bst-docker-import
Check if ``~/.local/bin`` appears in your PATH environment variable -- if it
@@ -44,7 +43,7 @@ called ``hello.bst`` assuming it is already built:
This script can also be used if you are running BuildStream inside Docker. In
this case, you will need to supply the command that you are using to run
BuildStream using the ``-c`` option. If you are using the
-`bst-here wrapper script <https://gitlab.com/BuildStream/buildstream/blob/master/contrib/bst-here>`_,
+`bst-here wrapper script <https://github.com/apache/buildstream/blob/master/contrib//bst-here>`_,
you can achieve the same results as the above example like this:
.. code:: bash
[buildstream] 04/08: doc/source/arch_sandboxing.rst: s/gitlab/github
Posted by tv...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tvb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/buildstream.git
commit ccd03ee8316020fa4dc6b750024ecac7721de04b
Author: Tristan van Berkom <tr...@codethink.co.uk>
AuthorDate: Tue Jan 5 18:00:27 2021 +0900
doc/source/arch_sandboxing.rst: s/gitlab/github
---
doc/source/arch_sandboxing.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/source/arch_sandboxing.rst b/doc/source/arch_sandboxing.rst
index 1399785..324c6ae 100644
--- a/doc/source/arch_sandboxing.rst
+++ b/doc/source/arch_sandboxing.rst
@@ -88,7 +88,7 @@ can be written and stored.
These restrictions are due to technical limitations. In future we hope to
support a wider range of filesystem metadata operations. See `issue #38
-<https://gitlab.com/BuildStream/buildstream/issues/38>`_ for more details.
+<https://github.com/apache/buildstream/issues/38>`_ for more details.
User and permissions model
~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -167,11 +167,11 @@ directory structure for each build job.
Some of the operations on filesystem metadata listed above are not prohibited
by the sandbox, but will instead be silently dropped when an artifact is
created. For more details see `issue #38
-<https://gitlab.com/BuildStream/buildstream/issues/38>`_.
+<https://github.com/apache/buildstream/issues/38>`_.
Some details of the host machine are currently leaked by this platform backend.
For more details, see `issue #262
-<https://gitlab.com/BuildStream/buildstream/issues/262>`_.
+<https://github.com/apache/buildstream/issues/262>`_.
Other POSIX systems
~~~~~~~~~~~~~~~~~~~
[buildstream] 03/08: COMMITTERS.rst: s/gitlab/github
Posted by tv...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tvb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/buildstream.git
commit 91c6dce83c0fa72764a35512d6b11a5456ab488e
Author: Tristan van Berkom <tr...@codethink.co.uk>
AuthorDate: Tue Jan 5 17:58:39 2021 +0900
COMMITTERS.rst: s/gitlab/github
---
COMMITTERS.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/COMMITTERS.rst b/COMMITTERS.rst
index fede276..bb5c07a 100644
--- a/COMMITTERS.rst
+++ b/COMMITTERS.rst
@@ -10,9 +10,9 @@ the BuildStream codebase. Note that this is not a full list of all
contributors.
+-----------------------------------+-----------------------------------+
-| Full Name | GitLab User |
+| Full Name | GitHub User |
+===================================+===================================+
-| Tristan Van Berkom | tristanvb |
+| Tristan Van Berkom | gtristan |
+-----------------------------------+-----------------------------------+
| Jürg Billeter | juergbi |
+-----------------------------------+-----------------------------------+
[buildstream] 07/08: doc/source/main_install.rst: s/gitlab/github
Posted by tv...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tvb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/buildstream.git
commit 24bfee7ad794ccd69a61ae288ff0f4f00e0fabe3
Author: Tristan van Berkom <tr...@codethink.co.uk>
AuthorDate: Tue Jan 5 18:15:00 2021 +0900
doc/source/main_install.rst: s/gitlab/github
---
doc/source/main_install.rst | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/source/main_install.rst b/doc/source/main_install.rst
index 0e47ccd..b9c26b4 100644
--- a/doc/source/main_install.rst
+++ b/doc/source/main_install.rst
@@ -207,7 +207,7 @@ to the latest dev snapshot like so::
Installing from a git checkout
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-To install directly from the `git repository <https://gitlab.com/BuildStream/buildstream.git>`_
+To install directly from the `git repository <https://github.com/apache/buildstream>`_
using python's ``pip`` package manager, you will additionally require:
- pip for python3 (only required for setup)
@@ -220,7 +220,7 @@ and determine which version you want to install.
Run the following commands::
- git clone https://gitlab.com/BuildStream/buildstream.git
+ git clone https://github.com/apache/buildstream.git
cd buildstream
git checkout <desired release tag>
pip3 install --user .
@@ -249,6 +249,7 @@ need to cleanly reinstall BuildStream::
git pull --rebase
pip3 install --user .
+
Installing in virtual environments
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can consider installing BuildStream in a
@@ -317,9 +318,9 @@ A regular way to do this is to add the following line to the end of your ``~/.ba
.. _install-container:
+
Buildstream Inside a Container
-------------------------------
-
If your system cannot provide the base requirements, it is possible to run
BuildStream within a container. This gives you an easy way to get started
using BuildStream on any Unix-like platform where containers are available,
[buildstream] 06/08: doc/source/hacking/ui.rst: s/gitlab/github
Posted by tv...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tvb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/buildstream.git
commit 044c9172260821854fbb17541339ae45e11c1b64
Author: Tristan van Berkom <tr...@codethink.co.uk>
AuthorDate: Tue Jan 5 18:07:49 2021 +0900
doc/source/hacking/ui.rst: s/gitlab/github
---
doc/source/hacking/ui.rst | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/doc/source/hacking/ui.rst b/doc/source/hacking/ui.rst
index e37dda4..cf33c55 100644
--- a/doc/source/hacking/ui.rst
+++ b/doc/source/hacking/ui.rst
@@ -3,7 +3,7 @@ Contributing to the UI
As we wish to cleanly separate BuildStream's core from the frontend, anything
user facing should be defined within the modules contained within the `_frontend
-<https://gitlab.com/BuildStream/buildstream/tree/master/src/buildstream/_frontend>`_
+<https://github.com/apache/buildstream/tree/master/src/buildstream/_frontend>`_
directory.
BuildStream's frontend includes:
@@ -19,9 +19,8 @@ BuildStream's frontend includes:
The command line interface
''''''''''''''''''''''''''
-
All of BuildStream's commands are defined within the module `cli.py
-<https://gitlab.com/BuildStream/buildstream/blob/master/src/buildstream/_frontend/cli.py>`_ -,
+<https://github.com/apache/buildstream/tree/master/src/buildstream/_frontend/cli.py>`_ -,
the main entry point which implements the CLI.
The command line interface is generated with `Click
@@ -64,9 +63,9 @@ To report messages back to the frontend, we use the ``Message()`` object
which is available from the ``Context``.
Supported message types are defined in `_message.py
-<https://gitlab.com/BuildStream/buildstream/blob/master/src/buildstream/_message.py>`_
+<https://github.com/apache/buildstream/tree/master/src/buildstream/_message.py>`_
and various uses of the messenger are defined in `_messenger.py
-<https://gitlab.com/BuildStream/buildstream/blob/master/src/buildstream/_messenger.py>`_
+<https://github.com/apache/buildstream/tree/master/src/buildstream/_messenger.py>`_
The ``Messenger`` class defines various methods which allow us to report back to
the frontend in particular ways. The common methods are: