You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildstream.apache.org by no...@apache.org on 2020/12/29 12:58:52 UTC

[buildstream] 03/06: doc/source/using_config.rst: Update documentation about default config file

This is an automated email from the ASF dual-hosted git repository.

not-in-ldap pushed a commit to branch tristan/bst2-separation
in repository https://gitbox.apache.org/repos/asf/buildstream.git

commit 8850b1608ab8ad0944b464bf9e500e1674570293
Author: Tristan Van Berkom <tr...@codethink.co.uk>
AuthorDate: Thu Apr 4 18:28:21 2019 +0900

    doc/source/using_config.rst: Update documentation about default config file
    
    Updated docs to mention the default configuration file is buildstream2.conf
---
 doc/source/using_config.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/source/using_config.rst b/doc/source/using_config.rst
index f8ef934..a415117 100644
--- a/doc/source/using_config.rst
+++ b/doc/source/using_config.rst
@@ -19,8 +19,8 @@ the default configuration.
 
 Unless a configuration file is explicitly specified on the command line when
 invoking ``bst``, an attempt is made to load user specific configuration from
-``$XDG_CONFIG_HOME/buildstream.conf``. On most Linux based systems, the location
-will be ``~/.config/buildstream.conf``
+``$XDG_CONFIG_HOME/buildstream2.conf``. On most Linux based systems, the location
+will be ``~/.config/buildstream2.conf``
 
 
 Project specific value
@@ -255,7 +255,7 @@ cache in the user configuration. This can be done in two ways:
 1. By restricting the maximum size of the cache directory itself.
 
 For example, to ensure that BuildStream's cache does not grow beyond 100 GB,
-simply declare the following in your user configuration (``~/.config/buildstream.conf``):
+simply declare the following in your user configuration (``~/.config/buildstream2.conf``):
 
 .. code:: yaml