Ryosuke Moro <szptvlfn%a-net.email.ne.jp@localhost> writes: > Hi, > > objection ? > -- > Ryosuke > > > Index: ffmpeg010/options.mk > =================================================================== > RCS file: /cvsroot/pkgsrc/multimedia/ffmpeg010/options.mk,v > retrieving revision 1.5 > diff -u -p -r1.5 options.mk > --- ffmpeg010/options.mk 14 Apr 2013 00:59:50 -0000 1.5 > +++ ffmpeg010/options.mk 20 Nov 2015 11:41:08 -0000 > @@ -4,7 +4,7 @@ > > PKG_OPTIONS_VAR= PKG_OPTIONS.ffmpeg010 > PKG_SUPPORTED_OPTIONS= faac lame libvpx opencore-amr theora vorbis x264 xvid > -PKG_SUGGESTED_OPTIONS= lame libvpx theora vorbis x264 xvid > +PKG_SUGGESTED_OPTIONS= lame theora vorbis x264 xvid > #PKG_OPTIONS_OPTIONAL_GROUPS= aac-decoder > #PKG_OPTIONS_GROUP.aac-decoder= faac I don't object, but I can't understand whether I should from your mail. - How much does this harm ffmpeg? What fraction of users would notice/care? - is there a plan to fix? by when?\ - How new is libvpx, and did upstream break backwards compat? If so, maybe it should be rolled back instead. * * We don't have a policy, but unstable upstreams are hard to deal with. A good start could be not updating them on release until we assess whether it is wise.
Description: PGP signature