You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sources of a package as well as the spec file are in git (example), the --build-in-place option for rpmbuild is quite convenient to build the package directly from the checkout directory. How does one know whether a spec file is meant for in-place building though? Esp when that someone is an automated build system calling rpmbuild?
Is it expected that the surrounding build system adds some extra metadata that tells it to use in-place building?
Should spec files have some tag that is understood by rpmbuild so it switches to in-place building automatically?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When sources of a package as well as the spec file are in git (example), the
--build-in-place
option forrpmbuild
is quite convenient to build the package directly from the checkout directory. How does one know whether a spec file is meant for in-place building though? Esp when that someone is an automated build system callingrpmbuild
?Is it expected that the surrounding build system adds some extra metadata that tells it to use in-place building?
Should spec files have some tag that is understood by
rpmbuild
so it switches to in-place building automatically?Beta Was this translation helpful? Give feedback.
All reactions