vcpkg/versions/l-/liblzf.json

{
  "versions": [
    {
      "git-tree": "0d228c25c072070365953245376aaed759a0ac95",
      "version": "3.6",
      "port-version": 1
    },
    {
      "git-tree": "ae07234a575d7c2f86990091df5aa34b9405143a",
      "version": "3.6",
      "port-version": 0
    }
  ]
}
[liblzf] New port (#37006) Adds liblzf: http://software.schmorp.de/pkg/liblzf.html [![Packaging status](https://repology.org/badge/tiny-repos/liblzf.svg)](https://repology.org/project/liblzf/versions) - [x] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md). - [x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines. - [x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all `find_package` calls are REQUIRED, are satisfied by `vcpkg.json`'s declared dependencies, or disabled with [CMAKE_DISABLE_FIND_PACKAGE_Xxx](https://cmake.org/cmake/help/latest/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html). - [x] The versioning scheme in `vcpkg.json` matches what upstream says. - [x] The license declaration in `vcpkg.json` matches what upstream says. - [x] The installed as the "copyright" file matches what upstream says. - [x] The source code of the component installed comes from an authoritative source. - [x] The generated "usage text" is accurate. See [adding-usage](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/examples/adding-usage.md) for context. - [x] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result. - [x] Only one version is in the new port's versions file. - [x] Only one version is added to each modified port's versions file. 2024-03-05 11:52:15 +02:00			`{`
			`"versions": [`
[vcpkg baseline][h5py-lzf] Update, use liblzf port, fix export, cleanup (#37332) Stop using vendored liblzf in h5py-lzf, fixing `lzf.h` install conflict. Alternative to https://github.com/microsoft/vcpkg/pull/37240. 2024-03-12 04:15:52 +01:00			`{`
			`"git-tree": "0d228c25c072070365953245376aaed759a0ac95",`
			`"version": "3.6",`
			`"port-version": 1`
			`},`
[liblzf] New port (#37006) Adds liblzf: http://software.schmorp.de/pkg/liblzf.html [![Packaging status](https://repology.org/badge/tiny-repos/liblzf.svg)](https://repology.org/project/liblzf/versions) - [x] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md). - [x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines. - [x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all `find_package` calls are REQUIRED, are satisfied by `vcpkg.json`'s declared dependencies, or disabled with [CMAKE_DISABLE_FIND_PACKAGE_Xxx](https://cmake.org/cmake/help/latest/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html). - [x] The versioning scheme in `vcpkg.json` matches what upstream says. - [x] The license declaration in `vcpkg.json` matches what upstream says. - [x] The installed as the "copyright" file matches what upstream says. - [x] The source code of the component installed comes from an authoritative source. - [x] The generated "usage text" is accurate. See [adding-usage](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/examples/adding-usage.md) for context. - [x] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result. - [x] Only one version is in the new port's versions file. - [x] Only one version is added to each modified port's versions file. 2024-03-05 11:52:15 +02:00			`{`
			`"git-tree": "ae07234a575d7c2f86990091df5aa34b9405143a",`
			`"version": "3.6",`
			`"port-version": 0`
			`}`
			`]`
			`}`