-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support package.cfg in rfpkg #18
Comments
this feature (support for package.cfg in dist-git) could be used for multilibs [1] ? |
No, that's a separate issue. But on second tough the implementation can share some bits. With package.cfg in dist-git, the aim is to submit the build twice one for the default target and another for another (twin) target. The way I plan to use this feature is with rpi and cuda namespaces at this step. In this feature, I wish I could use a package.cfg that would have some regexp to determine the appropriate target. (not to hardcode every fedora branches). The multilibs target is the same principle, but without building the default target. |
RFE forwarded to https://pagure.io/fedpkg/issue/354 |
https://pagure.io/fedpkg/blob/master/f/fedpkg/cli.py#_612 def register_build(self): https://pagure.io/fedpkg/blob/master/f/fedpkg/cli.py#_1247 def _build(self, sets=None): I think is this that is request in this issue, isn't it ? |
It's less important since package.cfg in epel8 is deprecated/unused and might disappear at some point... |
OK , I'm preparing a new rfpkg version here https://github.com/rpmfusion-infra/rfpkg/commits/fedpkg_sync_2021 |
Recently fedpkg gained support for package.cfg in dist-git
This file allows to submit a build for different koji targets
I want to re-use this feature for the rpi namespace (at least) where I want to have the package built twice (or more)
The text was updated successfully, but these errors were encountered: