-
Notifications
You must be signed in to change notification settings - Fork 379
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
Make -C the default for BuildOption(prep) #2998
Comments
Oh yup, thanks for filing this! The auto directory patch landed just after the buildsystem work so it kinda went under the radar, but it should complement the buildsystem work very nicely indeed. |
The new %(auto)setup -C option complements the declarative buildsystem very nicely: this is a trivial detail, don't bother the packager. While we can't default to it everywhere, Buildsystem is a great opportunity to do so. Suggested-by: Miro Hrončok <miro@hroncok.cz> Fixes: rpm-software-management#2998
The new %(auto)setup -C option complements the declarative buildsystem very nicely: this is a trivial detail, don't bother the packager. While we can't default to it everywhere, Buildsystem is a great opportunity to do so. Suggested-by: Miro Hrončok <miro@hroncok.cz> Fixes: #2998
Thanks. I noticed the |
Oh, thanks for pointing that out! I didn't even remember we have that in the documentation (although it was written by me, so ... age doesn't come alone as they say around here) |
Doubly more embarrassing as you mentioned that in the ticket description 😆 |
Maybe not the greatest example but at least something: 5d4a476 |
See #2997 (comment)
It would make sense to make
-C
the default option forBuildOption(prep)
, so packages utilizing the Declarative builds feature don't have to pass custom-n
to it. (Using custom-n
is also used as an example in the documentation forBuildOption(prep)
, so that will need a different example.)The text was updated successfully, but these errors were encountered: