spack/var/spack/repos/builtin/packages/poke/package.py

# Copyright 2013-2022 Lawrence Livermore National Security, LLC and other
# Spack Project Developers. See the top-level COPYRIGHT file for details.
#
# SPDX-License-Identifier: (Apache-2.0 OR MIT)


from spack.package import *


class Poke(AutotoolsPackage, GNUMirrorPackage):
    """"The extensible editor for structured binary data"""
    homepage = "https://www.jemarch.net/poke.html"
    gnu_mirror_path = 'poke/poke-1.0.tar.gz'

    maintainers = ['ChristianTackeGSI']

    version('1.0', sha256='de930b8700c0772b3c2cd0d0ca35f50fd3d77bdf82c6251eb516b49e8ca25b0a')

    depends_on('pkgconfig')
    depends_on('readline')
    depends_on('bdw-gc')
    depends_on('json-c')

    build_directory = 'spack-build'
Update copyright year to 2022 2022-01-13 03:21:41 +08:00			`# Copyright 2013-2022 Lawrence Livermore National Security, LLC and other`
poke: new package at v1.0 (#22085) 2021-03-05 00:41:48 +08:00			`# Spack Project Developers. See the top-level COPYRIGHT file for details.`
			`#`
			`# SPDX-License-Identifier: (Apache-2.0 OR MIT)`


refactor: packages import `spack.package` explicitly (#30404) Explicitly import package utilities in all packages, and corresponding fallout. This includes: * rename `spack.package` to `spack.package_base` * rename `spack.pkgkit` to `spack.package` * update all packages in builtin, builtin_mock and tutorials to include `from spack.package import ` update spack style * ensure packages include the import * automatically add the new import and remove any/all imports of `spack` and `spack.pkgkit` from packages when using `--fix` * add support for type-checking packages with mypy when SPACK_MYPY_CHECK_PACKAGES is set in the environment * fix all type checking errors in packages in spack upstream * update spack create to include the new imports * update spack repo to inject the new import, injection persists to allow for a deprecation period Original message below: As requested @adamjstewart, update all packages to use pkgkit. I ended up using isort to do this, so repro is easy: ```console $ isort -a 'from spack.pkgkit import ' --rm 'spack' ./var/spack/repos/builtin/packages//package.py $ spack style --fix ``` There were several line spacing fixups caused either by space manipulation in isort or by packages that haven't been touched since we added requirements, but there are no functional changes in here. * [x] add config to isort to make sure this is maintained going forward 2022-05-29 00:55:44 +08:00			`from spack.package import *`


poke: new package at v1.0 (#22085) 2021-03-05 00:41:48 +08:00			`class Poke(AutotoolsPackage, GNUMirrorPackage):`
			`""""The extensible editor for structured binary data"""`
start of work to add spack audit packages-https checker (#25670) This PR will add a new audit, specifically for spack package homepage urls (and eventually other kinds I suspect) to see if there is an http address that can be changed to https. Usage is as follows: ```bash $ spack audit packages-https <package> ``` And in list view: ```bash $ spack audit list generic: Generic checks relying on global variables configs: Sanity checks on compilers.yaml Sanity checks on packages.yaml packages: Sanity checks on specs used in directives packages-https: Sanity checks on https checks of package urls, etc. ``` I think it would be unwise to include with packages, because when run for all, since we do requests it takes a long time. I also like the idea of more well scoped checks - likely there will be other addresses for http/https within a package that we eventually check. For now, there are two error cases - one is when an https url is tried but there is some SSL error (or other error that means we cannot update to https): ```bash $ spack audit packages-https zoltan PKG-HTTPS-DIRECTIVES: 1 issue found 1. Error with attempting https for "zoltan": <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'www.cs.sandia.gov'. (_ssl.c:1125)> ``` This is either not fixable, or could be fixed with a change to the url or (better) contacting the site owners to ask about some certificate or similar. The second case is when there is an http that needs to be https, which is a huge issue now, but hopefully not after this spack PR. ```bash $ spack audit packages-https xman Package "xman" uses http but has a valid https endpoint. ``` And then when a package is fixed: ```bash $ spack audit packages-https zlib PKG-HTTPS-DIRECTIVES: 0 issues found. ``` And that's mostly it. :) Signed-off-by: vsoch <vsoch@users.noreply.github.com> Co-authored-by: vsoch <vsoch@users.noreply.github.com> 2021-09-02 14:46:27 +08:00			`homepage = "https://www.jemarch.net/poke.html"`
poke: new package at v1.0 (#22085) 2021-03-05 00:41:48 +08:00			`gnu_mirror_path = 'poke/poke-1.0.tar.gz'`

			`maintainers = ['ChristianTackeGSI']`

			`version('1.0', sha256='de930b8700c0772b3c2cd0d0ca35f50fd3d77bdf82c6251eb516b49e8ca25b0a')`

Fix pkgconfig dependencies (#22702) pkgconfig is the correct virtual provider. 2021-04-02 07:45:01 +08:00			`depends_on('pkgconfig')`
poke: new package at v1.0 (#22085) 2021-03-05 00:41:48 +08:00			`depends_on('readline')`
			`depends_on('bdw-gc')`
			`depends_on('json-c')`

			`build_directory = 'spack-build'`