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?
-- Kind regards, Jeroen van Meeuwen -kanarip -- http://www.kanarip.com/ RHCE, LPIC-2, MCP, CCNA C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
