Michael Schwendt wrote : > A circular dependency is the wrong way of thinking here. Probably it's > only applied because end-users are confronted with data package names and > might try low-level commands like "yum install somegame-data" instead of > telling an installer to add/remove "somegame". Well, one might argue that without a circular dependency, end-users are confronted with a possibly unexpected behaviour : yum install gamename (pulls-in huge gamename-data) yum remove gamename (leaves huge gamename-data installed...) I'm not saying that a circular dependency is the right solution, but it is indeed the only easy one I see. Matthias > (In networked multi-machine installations it would even be plausible to > remove the dependency on the game data package, as it might be installed > only on a file server.) And see bug reports flowing in... for anyone who might be facing that scenario, I'd suggest either installing with --nodeps or installing the game itself anyway :-) Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora Core release 6 (Zod) - Linux kernel 2.6.18-1.2835.fc6 Load : 0.33 0.29 0.26 -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
