What about trigger versioning, i.e. let's say one for foo < 1.0 and another for foo >= 2.0, this will probably prohibit specifying them as if I read the commit correctly it looks for package names only, no?
Not preventing multiple for same package but just running them all would be another approach, see comment 2.
https:/ /github. com/rpm- software- management/ rpm/commit/ 3ae1c414f69a0ed dbfecd4341dd27c 7a5e90e12a
What about trigger versioning, i.e. let's say one for foo < 1.0 and another for foo >= 2.0, this will probably prohibit specifying them as if I read the commit correctly it looks for package names only, no?
Not preventing multiple for same package but just running them all would be another approach, see comment 2.
BTW, what's upstream nowadays? The fix seems to be in https:/ /github. com/rpm- software- management/ rpm but http:// rpm.org/ wiki/GetSource still says git is at http:// rpm.org/ git/