-----BEGIN PGP SIGNED MESSAGE-----
On 01/28/2016 02:13 PM, John Florian wrote:
Woot; success! After several failed attempts, I got to:
$ koji add-tag-inheritance --priority=2 f21-build f21-released $
koji list-tag-inheritance f21-build f21-build (7) ├─f21 (6) │
└─f20 (1) └─f21-released (10)
I tried a scratch build targeting f21 and now my BuildRequires is
satisfied through inheritance of f21-released and it worked. So to
test my understanding, I believe:
* having f21 inherit from f20 is mostly useful so that you don't
have to "koji add-pkg ..." (and likely more) everything again.
* inheritance also allows the parent tags of a build tag help
resolve build deps
Please correct me if I'm wrong.
Looks like a good set up to me.
Also the priorities involved in inheritance are a bit mysterious.
I merely guessed at a priority when adding the inheritance above.
I don't see any means from the CLI with which to show the
inheritance priorities, nor any indication if a lower number
indicates a lower or a higher priority.
When Koji looks for a package, it does a depth-first search.
(f21-build, f21, f20, f21-released is the order in your case) The
priority influences the ordering. They're just arbitrary numbers. I
usually use multiples of 10 to start, so that if I ever need to inject
a tag, I can pick a priority in between the tags that are already there.
The numbers you see in list-tag-inheritance in the parentheses are tag
IDs, not priority, in case that is confusing you.
- - Jay
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
-----END PGP SIGNATURE-----