Re: [Rpm-maint] [rpm-software-management/rpm] Understanding of the Declarative builds, Python edition (Discussion #2997)

2024-04-10 Thread Panu Matilainen
FWIW, turns out this stuff is pretty crippled in the alpha release due to these two issues: https://github.com/rpm-software-management/rpm/issues/3024 https://github.com/rpm-software-management/rpm/issues/2204 They don't prevent one from developing buildsystems but pretty much prevent using

Re: [Rpm-maint] [rpm-software-management/rpm] Understanding of the Declarative builds, Python edition (Discussion #2997)

2024-03-28 Thread Panu Matilainen
FWIW, I revived my rpm-snapshot repository where you can get Fedora compatible builds from rpm git: https://copr.fedorainfracloud.org/coprs/pmatilai/rpm-snapshot/ so if folks want to try this out before the soon-to-be-released 4.20 alpha, there goes. -- Reply to this email directly or view it

Re: [Rpm-maint] [rpm-software-management/rpm] Understanding of the Declarative builds, Python edition (Discussion #2997)

2024-03-27 Thread Panu Matilainen
On that note, don't hesitate to point out shortcomings or other new related ideas. I'm too close to the source (in both meanings :smile: ) to see clearly, as the -C example points out. -- Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Understanding of the Declarative builds, Python edition (Discussion #2997)

2024-03-26 Thread Miro Hrončok
https://github.com/rpm-software-management/rpm/issues/2998 -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/discussions/2997#discussioncomment-8919866 You are receiving this because you are subscribed to this thread. Message ID:

Re: [Rpm-maint] [rpm-software-management/rpm] Understanding of the Declarative builds, Python edition (Discussion #2997)

2024-03-26 Thread Panu Matilainen
That would be good so it wont go forgotten, yeah. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/discussions/2997#discussioncomment-8916709 You are receiving this because you are subscribed to this thread. Message ID:

Re: [Rpm-maint] [rpm-software-management/rpm] Understanding of the Declarative builds, Python edition (Discussion #2997)

2024-03-26 Thread Miro Hrončok
Should I open an issue for -C to be the default for BuildOption(prep)? -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/discussions/2997#discussioncomment-8916583 You are receiving this because you are subscribed to this thread. Message ID:

Re: [Rpm-maint] [rpm-software-management/rpm] Understanding of the Declarative builds, Python edition (Discussion #2997)

2024-03-26 Thread Miro Hrončok
As long as it won't tell me `Unknown option l in buildsystem_pyproject_install` but let me pass any option further down via `%**`, good (even better, so I won't have to duplicate the option list). -- Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Understanding of the Declarative builds, Python edition (Discussion #2997)

2024-03-26 Thread Panu Matilainen
That's the essence of it, yes. One thing that did catch my eye: the %buildsystem_foo_install() and such macros do not take options currently because they'd be shared across all buildsystems. So eg `%buildsystem_pyproject_check(e:t)` will not do what you intend, there's no way to pass options

[Rpm-maint] [rpm-software-management/rpm] Understanding of the Declarative builds, Python edition (Discussion #2997)

2024-03-26 Thread Miro Hrončok
Hello. I've just located https://github.com/rpm-software-management/rpm/issues/1087 in https://fedoraproject.org/wiki/Changes/RPM-4.20 and I've read https://rpm-software-management.github.io/rpm/manual/buildsystem.html I am trying to understand how to use this, so let's dive in. Suppose I