[jhalfs] branch trunk updated (f756851 -> 1870b56)

"Git Owner" ([email protected] via alfs-discuss Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.automated
Message-ID <163751968429.17562.4195270437194334466@rivendell.linuxfromscratch.org>
This is an automated email from the git hooks/post-receive script.

git pushed a change to branch trunk
in repository jhalfs.

    from f756851  BLFS tools: do not needlessly validate book
     new 2b3edd2  [Remove BLFS envars.conf]: new gen_config.xsl
     new 60e539b  Remove KBLAYOUT setting
     new 9daa202  BLFS tools: Take variables from config instead of envars.conf
     new 0a93085  BLFS tools: Do not source envars.conf
     new 5fd1a98  Remove BLFS/envars.conf
     new b0965fa  BLFS tools: Source /etc/profile in scripts
     new 267b19d  Adapt func_install_blfs.sh to the removal of envars
     new 0495e57  Update README.BLFS for envars.conf removal
     new 1870b56  Ensure that MAKE_TERM(OUT|ERR) are unset

The 9 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:
 BLFS/envars.conf              |  99 -------------------
 BLFS/gen-makefile.sh          |   2 +-
 BLFS/gen_pkg_book.sh          |  56 ++++++++---
 BLFS/xsl/gen_config.xsl       | 173 ++++++++++++++++++++++-----------
 BLFS/xsl/scripts.xsl          | 163 ++++++++++++++++++++++++++-----
 README.BLFS                   | 221 ++++++++++++++++++++++--------------------
 common/libs/func_install_blfs |  13 +++
 7 files changed, 434 insertions(+), 293 deletions(-)
 delete mode 100644 BLFS/envars.conf

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.