https://bugzilla.redhat.com/show_bug.cgi?id=1020942 --- Comment #25 from Richard Shaw <hobbes1069@xxxxxxxxx> --- (In reply to Jeremy Newton from comment #24) > (In reply to Richard Shaw from comment #23) > > Ok, I've updated my spec file based on the comments so far but I want to > > make sure it's not possible/practical to create a parallel installable devel > > package before we implement a Conflict with it. > > > > The bakefiles can be moved (is there something that needs to be updated to > > point to the new location?) > > > > wx-config can be renamed wx-config-3.0 OR we can see what it would take to > > create a wrapper that's not only multi-lib aware but version aware? > > > > wxwin.m4 can be renamed, but like the bakefiles, is there anything that > > assumes it's location that can't be fixed at build time? > > Is there a reason a conflict should be avoided? Well it should always be avoided if it's avoidable :) But in all seriousness... What if you need to be able to develop programs for both libraries outside of a mock build environment? Are you supposed to yum erase / yum install back and forth? > It seems building with GTK3 causes a build failure for F20 (though it builds > fine on F19): Yes, I found a patch for it upstream and applied it. I'm getting good builds for rawhide in mock. -- 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