Opened 3 weeks ago
Closed 40 hours ago
#6003 closed enhancement (fixed)
pkgconf-3.0.7
| Reported by: | Bruce Dubbs | Owned by: | lfs-book |
|---|---|---|---|
| Priority: | normal | Milestone: | 13.2 |
| Component: | Book | Version: | git |
| Severity: | normal | Keywords: | |
| Cc: |
Description
New point version.
Change History (3)
comment:1 by , 11 days ago
| Summary: | pkgconf-3.0.6 → pkgconf-3.0.7 |
|---|
comment:2 by , 42 hours ago
Changes from 3.0.6 to 3.0.7:
- Correctness fixes:
- spdxtool now serializes the SPDX 3.0 suppliedBy property as a single Agent reference instead of a one-element array, as required by the official JSON schema.
- bomtool no longer emits PackageDownloadLocation twice for each package.
- Build, packaging and portability fixes:
- The Windows installer uses a default installation directory without a space in its name.
- Skip the spdxtool allocation-failure test for static builds, where linker wrapping also intercepts libpkgconf allocations and invalidates the test.
- Use PKGCONF_ITEM_SIZE instead of PATH_MAX in the test runner, allowing it to build on systems where PATH_MAX is not declared, such as GNU Hurd.
Changes from 3.0.5 to 3.0.6:
- Command-line behavior:
- --variable accepts multiple modules and prints the requested variable's value for each module, in argument order. --path and --print-variables remain limited to a single module.
- pccritic no longer reports the PC061 style finding for CRLF line endings, avoiding a noisy warning for normal Windows files.
- Build and portability fixes:
- Improve OS/2 support by exporting libpkgconf APIs from DLL builds, recognizing OS/2 drive letters and path separators, comparing paths without case sensitivity, and using binary mode for redirected standard output and error.
- Declare pkgconf long-path-aware in its Windows application manifest, allowing paths beyond the traditional MAX_PATH limit when long paths are enabled by the operating system.
Note:
See TracTickets
for help on using tickets.

Now version 3.0.7,