aboutsummaryrefslogtreecommitdiff
path: root/tests/store-deduplication.scm
diff options
context:
space:
mode:
authorRaghav Gururajan <rg@raghavgururajan.name>2022-04-17 04:57:15 -0400
committerRaghav Gururajan <rg@raghavgururajan.name>2022-04-17 05:03:00 -0400
commite5174200c4d78358e22e889da2b53dc06c202003 (patch)
treec5c53eefcad9fce653cb08246916553f2f355572 /tests/store-deduplication.scm
parent0c89fe9e17dc9e628c73959289464ac5f146c7cd (diff)
downloadguix-e5174200c4d78358e22e889da2b53dc06c202003.tar.gz
guix-e5174200c4d78358e22e889da2b53dc06c202003.zip
gnu: gnucash: Update to 4.10.
Variables gnucash and gnucash-docs have to be updated together. * gnu/packages/gnucash.scm (gnucash)[version]: Update to 4.10. (gnucash-docs)[version]: Update to 4.10. [build-system]: Migrate from gnu to cmake. [arguments]: Disable tests.
Diffstat (limited to 'tests/store-deduplication.scm')
0 files changed, 0 insertions, 0 deletions
ires.txt): Adapt. Maxim Cournoyer 2019-07-02import: pypi: Do not parse optional requirements from source....* guix/import/pypi.scm: Export PARSE-REQUIRES.TXT. (clean-requirement): Move procedure to the top level. (guess-requirements): Move the READ-REQUIREMENTS procedure to the top level, and rename it to PARSE-REQUIRES.TXT. Move the CLEAN-REQUIREMENT procedure to the top level. Move the COMMENT? functions inside the PARSE-REQUIRES.TXT procedure. (parse-requires.txt): Add a SECTION-HEADER? predicate, and use it to prevent parsing optional requirements. * tests/pypi.scm (test-requires-with-sections): New variable. ("parse-requires.txt, with sections"): New test. Maxim Cournoyer 2019-07-02tests: pypi: Mute the output of tar....The output of tar when creating archives for the purpose of tests is not useful, so we mute it. * tests/pypi.scm ("pypi->guix-package"): Mute the output of tar. ("pypi->guix-package, wheels"): Likewise. Maxim Cournoyer 2019-07-02import: pypi: Do not consider requirements.txt files....PyPI packages are mandated to have a setup.py file, which contains a listing of the required dependencies. The setuptools/distutils machinery embed metadata in the archives they produce, which contains this information. There is no need nor gain to collect the requirements from a "requirements.txt" file, as it is not the true record of dependencies for PyPI packages and may contain extraneous requirements or not exist at all. * guix/import/pypi.scm (guess-requirements): Update comment. [guess-requirements-from-source]: Do not attempt to parse the file requirements.txt. Streamline logic. * tests/pypi.scm (test-requires.txt): Rename from test-requirements, to hint at the file being tested. ("pypi->guix-package"): Adapt so that the fake package contains a requires.txt file rather than a requirements.txt file. ("pypi->guix-package, wheels"): Likewise. Maxim Cournoyer