I'd like to see tests with real-world bconds in packages. We already have tests
for bcond so this can build on top of those.
I'd like to see documentation and tests on how this is supposed to be used in
real life, answering some practical matters like
- Where would the overrides/defaults be stored, a macro file somewhere in the
path?
- Would it be shipped to users so that when you rebuild an src.rpm you get the
same selections as the distro build?
- If I have a bcond set in a spec, overridden to something else by the distro,
can I override the distro setting by by a "--with/without foo" on the command
line? This seems crucial if the defaults are shipped to users.
Everything is of course simpler if these overrides are only selectively passed
by a command line in a central buildsys somewhere, reading up from its own
config in whatever format. It makes for an inconsistent rebuild behavior though.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2405#issuecomment-1923586931
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2405/c1923586...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
