andrew/libakstdlib
1
0
Fork 0
Code Issues 26 Pull Requests Actions Packages Projects Releases Wiki Activity

libakerror installs no akerrorConfigVersion.cmake, so the 1.0.0 floor cannot be expressed #5

New Issue
Open
opened 2026-08-02 18:53:18 -04:00 by tachikoma · 0 comments
tachikoma commented 2026-08-02 18:53:18 -04:00
Collaborator
Copy Link

Source: TODO.md §1.4 (at 669b2b3)

Consequence here. cmake/akstdlib.cmake.in has to call
find_dependency(akerror) with no version, because a request for one would be
refused for want of a version file no matter what is installed.

The 1.0.0 floor therefore rests on akstdlib.pc's Requires: and the #error
guard in akstdlib.h, neither of which covers a find_package consumer.

What closing it would touch. One write_basic_package_version_file() call
upstream -- libakstdlib already does this correctly and can be copied -- then add
the 1.0.0 floor to the find_dependency here.

Not fixable from inside this repository.

Files: cmake/akstdlib.cmake.in, deps/libakerror/CMakeLists.txt

Filed by Tachikoma (Claude Code, Opus 5, 1M context)

**Source:** TODO.md §1.4 (at 669b2b3) **Consequence here.** `cmake/akstdlib.cmake.in` has to call `find_dependency(akerror)` **with no version**, because a request for one would be refused for want of a version file no matter what is installed. The 1.0.0 floor therefore rests on `akstdlib.pc`'s `Requires:` and the `#error` guard in `akstdlib.h`, **neither of which covers a `find_package` consumer.** **What closing it would touch.** One `write_basic_package_version_file()` call upstream -- libakstdlib already does this correctly and can be copied -- then add the `1.0.0` floor to the `find_dependency` here. Not fixable from inside this repository. **Files:** `cmake/akstdlib.cmake.in`, `deps/libakerror/CMakeLists.txt` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 0.3.0 milestone 2026-08-02 18:53:18 -04:00
tachikoma added the packagingblast-radius:mediumstatus::grooming labels 2026-08-02 18:53:18 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abi-break
Cannot land without a soname bump
 api-gap
A caller cannot express something
 blast-radius:high
Ordering: highest blast radius
 blast-radius:low
Ordering: lowest blast radius
 blast-radius:medium
Ordering: middling blast radius
 defect
Wrong behaviour reachable from the public API
 design-decision
Needs a decision written down before code
 docs
Documentation, comments, AGENTS.md
 hygiene
Style, dead code, consistency
 packaging
Build, install, pkg-config, CMake config
 performance
Has a measurement behind it
 status::blocked
Waiting on something else -- a decision, a dependency, or another issue
 status::grooming
Not yet worked out: scope, approach or priority still being settled
 status::ready
Understood well enough to start: scope and approach are settled
 test-coverage
A gap in the suites, not a defect
No Label blast-radius:medium packaging status::grooming
Milestone
No items
No Milestone 0.3.0
Projects
Clear projects
No project
Assignees
Clear assignees
tachikoma andrew
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: andrew/libakstdlib#5
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?