https://bugzilla.redhat.com/show_bug.cgi?id=1150566 --- Comment #23 from Christopher Meng <i@xxxxxxxx> --- (In reply to awilliam@xxxxxxxxxx from comment #22) > they're from the same upstream vendor, but not the same upstream repository. > strictly they ought to be packaged separately I believe. lurlparser is > clearly intended to potentially be of use outside of wcmcommander, or it > wouldn't be its own repository with its own release. IMO No, another similar case is redis, it contains linenoise, which is written by redis upstream and blindly favored/stared by lots of people. I personally think it's pretty general and not good, unlike how redis has been favored. But upstream still uses it. Some upstreams intend to seperate everything they have, in order to show the distinct usage of various subprojects, however then bundle subprojects into another subprojects to make them work together. I'd observe this, most of upstreams know their code better than downstream packagers, if upstream can't even handle problems correct, downstream can't handle them as well. What I'm going to do is to open a PR and use git submodule functionality to force upstream to keep the code up to date, and motivate them to check the compatibilities before each new release of wcm. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review