On Mon, Aug 13, 2012 at 1:17 PM, Cristian Morales Vega <[email protected]> wrote: > Hi, > > The thing is I don't really use mlt, kdenlive, openshot or anything > related so I don't know a few things. Basically I need to know what a > program linked to libmlt.so.X can expect to be available. I guess > everything under /usr/lib64/mlt/ is optional, true? Even > /usr/lib64/mlt/libmltcore.so? But then what about the things under
core is virtually required - both lib and its corresponding dir under share > /usr/share/mlt/? Most of it is clearly module related, but what about correct, and share/metaschema.yml is not really required by anything except the kwalify YAML validation tool for people who may want to contribute service metadata (plugin docs) to the project. > /usr/share/mlt/presets/ and /usr/share/mlt/profiles/? Should I package profiles are also virtually required, but not presets, but perhaps they are not worth making a separate package. > mlt in a way that having /usr/lib64/libmlt.so.X installed requires > having presets and profiles also installed? I said "virtually" because strictly they (core and profiles) are not required, but MLT's usefulness is practically nil without it. Some would argue that avformat is practically required, but without it, one could still work with still images, DV, and Vorbis through other modules, and I realize some distros want to separate out the avformat module into a different repository or loosely affiliated project. -- +-DRD-+ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
