>>>>> "PR" == Pavel Raiskup <praiskup@xxxxxxxxxx> writes: PR> The design issue (probably hard to solve) is that there is no PR> automatic way to _not_ include such package into particular ARCH yum PR> repo; and we rather bother packagers. I'm not entirely sure how the compose tools would that a particular dependency issue is intentional. I guess it could take a complete set of all packages which have any ExcludeArch: or ExclusiveArch: tags and chase the dependency tree of each backwards to see if it hits any of those. Which is certainly a nontrivial thing but I guess if someone really wanted to write it.... - J< _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
