On Thu, Mar 15, 2007 at 10:26:09PM -0400, Jesse Keating wrote: > > How hard is it to get a program added to the blacklist? Festival probably > > should be. And then I should do: > > %ifarch x86_64 > > Obsoletes: festival.i386 < 1.96 > > %endif > First, I don't think you can reference arch like that in a spec. My understanding is that you can, as of 4.4.1. > Secondly, why don't you split out the two libs into a festival-libs package, > that is required by festival? festival-devel will pick up the library > requires out of the -libs package, the libs package will have a generic > requires on festival, not an arch specific one. This will leave > festival-devel and festival-libs as multiarch, while festival itself is not. > This is the solution that many other packages use. Hmmmm. Y'know, actually, I've already done that in the updated package. Well then. That's less annoying. :) But, I think I'll still need the above incantation to make upgrades work cleanly, right? Because otherwise, there'll be no upgrade target for the previous festival.i386 package on x86_64 systems. Or am I not thinking straight? It's been a long day. On another front, it turns out that there's a "libFestival.a" which hasn't been packaged for several years which would really need to be included for the devel package to be useful _at all_. Still thinking about what to do about that. :) -- Matthew Miller mattdm@xxxxxxxxxx <http://mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/> -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
