On Sat, 2007-10-20 at 21:44 +0200, Jeroen van Meeuwen wrote: > Stewart Adam wrote: > > Hi, > > > > Since xine-lib has been moved to Fedora, I realized so could totem-xine. > > I've been working on a totem spec that includes both gstreamer and xine > > backends. As of now, the spec generates the usual subpackages plus > > 'totem-gstreamer' and 'totem-xine' which contain the binaries for the > > gstreamer- and xine-based binary totem. I've used --program-suffix at > > compile time, so they are parallel installable. > > > > What do you think the best approach is to packaging this, if at all? Two > > options I'm thinking of are having the two engines conflict or using > > alternatives to have a configurable backend (switching "on demand"). > > > > Stewart > > > > I've not read the entire thread yet but does this apply to > totem-xine-plarser and totem-plparser as well? That's a side-effect of having 2 different source RPMs. There won't be 2 packages containing the exact same library anymore. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
