Cristian Le
Cristian Le
The issue I am thinking of solving is to have a way to inject some `LD_LIBRARY_PATH` or `PATH` so that it accounts for the path discrepancy of CMake installed files...
Although all settings are mapped to the python object, just to avoid possible confusion it would be nice to generate the original configuration options [^1] as well, something like ````markdown...
Back in #790 I commented that we could support `configurePresets` if we overwrite the `binarydir`. It seems to work fine, but I realized we still have an issue to discuss...
It occurred to me that we should support dynamic license field because a user project might either bundle or link to a library which would change the license metadata. A...
The usecase for this is when we are building the documentation and using `autodoc` to avoid import failures and avoid cmake building. The user could have something like this setup...
An example of a project that would benefit from this is `rapidfuzz` which can be optimized for different `x86_64-vX` versions [^1]. Fedora is also investigating how to provide multiple versions...
This is a tracker issue for devendoring `pyproject_metadata`. Currently scikit-build-core uses the latest versions of `pyproject_metadata` and it can affect the checksums of the tests, so it makes sense to...
### Description A fun edge-case, I have submitted a PR to retire a package [^1], but the CI is still executing on those. Would be nice to early exit in...
### Description Let's take `/packit pull-from-upstream --with-pr-config` workflow for example. Currently the workflow with `pagure` is that each time the user and packit take turn to post a comment resulting...
Add a flag for `/packit pull-from-upstream` to include files or commit from the `--with-pr-config`
### Description Example case is in `rust2rpm`, sometimes we want to make some changes to the `rust2rpm.toml` and then rerun it with those changed files/manually created patches etc. In this...