diff options
| author | Ulf Magnusson <ulfalizer@gmail.com> | 2018-07-10 09:13:07 +0200 |
|---|---|---|
| committer | Ulf Magnusson <ulfalizer@gmail.com> | 2018-07-10 09:13:54 +0200 |
| commit | 8ff1be9dcf7d7d30fce553b0ed21b40bbc26cae7 (patch) | |
| tree | b5ba819a0f609cdd80e604d6ba0d88e0607043ad | |
| parent | 9ae09d5a5c6c69c089f76eb0b7ce3bbcb690257d (diff) | |
Make 8.0.0 releasev8.0.0
New features:
- 2433deb ("Add Kconfig preprocessor") implements a new Kconfig
preprocessor, documented in
https://github.com/torvalds/linux/blob/master/Documentation/kbuild/kconfig-macro-language.txt.
It is required to parse the linux-next Kconfigs now, and will appear
in Linux 4.18.
'option env=...' symbols and the $FOO syntax for expanding
environment variables will be supported for backwards compatibility
for a while. Consider switching to $(FOO) though, which is the new
syntax (and removing 'option env=...' symbols).
Changed behavior:
- c19fc11 ("Drop some compatibility and tighten up lexing") makes
Kconfiglib flag invalid characters in Kconfig files as a syntax
error in all context. They were previously ignored in some places
for compatibility with old sloppy versions of the C tools.
The C tools fixed it with commit c2264564 ("kconfig: warn of
unhandled characters in Kconfig commands") in July 2015. Older
kernels might require fixing up the Kconfig files a bit now.
New warnings:
- 4200e25 ("Generalize select-with-unsatisfied-deps warning") makes
the select-with-unsatisfied-dependencies warning trigger when a
symbol with m-valued direct dependencies is y-selected.
| -rw-r--r-- | README.rst | 11 | ||||
| -rw-r--r-- | setup.py | 2 |
2 files changed, 7 insertions, 6 deletions
@@ -70,17 +70,18 @@ available in the Python 2 version of the standard ``curses`` module. that your ``PATH`` includes the directory where the executables end up. You can list the installed files with ``pip(3) show -f kconfiglib``. -All releases have a corresponding tag in the git repository, e.g. ``v7.0.0`` +All releases have a corresponding tag in the git repository, e.g. ``v8.0.0`` (the latest version). `Semantic versioning <http://semver.org/>`_ is used. There's been -five small changes (`1 <https://github.com/ulfalizer/Kconfiglib/commit/e8b4ecb6ff6ccc1c7be0818314fbccda2ef2b2ee>`_, +six small changes (`1 <https://github.com/ulfalizer/Kconfiglib/commit/e8b4ecb6ff6ccc1c7be0818314fbccda2ef2b2ee>`_, `2 <https://github.com/ulfalizer/Kconfiglib/commit/db633015a4d7b0ba1e882f665e191f350932b2af>`_, `3 <https://github.com/ulfalizer/Kconfiglib/commit/8983f7eb297dd614faf0beee3129559bc8ba338e>`_, `4 <https://github.com/ulfalizer/Kconfiglib/commit/cbf32e29a130d22bc734b7778e6304ac9df2a3e8>`_, -`5 <https://github.com/ulfalizer/Kconfiglib/commit/eb6c21a9b33a2d6e2bed9882d4f930d0cab2f03b>`_) -to the behavior of the API (which shouldn't affect many people), which is why -the major version is at 7 rather than 2. +`5 <https://github.com/ulfalizer/Kconfiglib/commit/eb6c21a9b33a2d6e2bed9882d4f930d0cab2f03b>`_, +`6 <https://github.com/ulfalizer/Kconfiglib/commit/c19fc11355b13d75d97286402c7a933fb23d3b70>`_) +to the behavior of the API, which is why the major version is at 8 rather than +2. I do major version bumps for all behavior changes, even tiny ones. Manual installation ~~~~~~~~~~~~~~~~~~~ @@ -4,7 +4,7 @@ import setuptools setuptools.setup( name="kconfiglib", # MAJOR.MINOR.PATCH, per http://semver.org - version="7.0.0", + version="8.0.0", description="A flexible Python Kconfig parser", long_description= open(os.path.join(os.path.dirname(__file__), "README.rst")).read(), |
