Dalibor Pospíšil

one more possible extension would be usage of _path_ attribute which would allow one to use just a sub-tree of the target repo which could be another form of filtering...

I think I have another use case: as a tester of component _A_ I want to include on test of component _B_ to my scope. Typically I would like to...

Yep, looks like the idea is basically the same. The difference might be the granularity.

hm, maybe it works but still I do not understand why: ``` $ fmf ls --condition '"Fedora_missing_external_dependencies" in tag' /usbguard/Sanity/selinux $ fmf ls --condition '"Fedora_missing_external_dependencies" not in tag' /usbguard/Sanity/config-sanity ```

I think I found it - if the tag does not exist at all then even the not presence is false. If I define an empty tag in the root...

Just to be sure the keys of the object are simply python variables which can be used in the condition, right? E.g. the afore mentioned condition can be written like...

After some thinking I must say that if this is implemented it should be done on tmt side. Simply `+require` would be treated as any other attribute (redefining, adding, deducting...