spacepaste

  1.  
  2. eselect news read
  3. 2015-02-01-use-libav
  4. Title ffmpeg/libav conflict management:
  5. USE=libav
  6. Author Michał Górny <mgorny@gentoo.org>
  7. Posted 2015-02-01
  8. Revision 2
  9. The support for automatic choice between ffmpeg and libav is going to be
  10. deprecated in favor of explicit choice via USE flags. This change aims
  11. to solve multiple repeating issues, including Portage undesirably
  12. wanting to replace one package with the other, lack of proper reverse
  13. dependency on ffmpeg/libav upgrades and some of the hard-to-understand
  14. upgrade failures involving blockers. It also may be used to make ffmpeg
  15. and libav co-installable in the future.
  16. The current USE=ffmpeg will maintain its role of enabling optional
  17. support for ffmpeg or a compatible implementation (libav) in a package.
  18. However, whenever appropriate additional USE=libav will be introduced to
  19. control the preference of one implementation over the other.
  20. Users who currently use libav need to enable USE=libav in
  21. /etc/portage/make.conf. It should be noted that users still need to
  22. enable USE=ffmpeg on packages with optional libav support as well.
  23. Users who currently use ffmpeg need to take no action.
  24. Please also note that some packages support only one of the two
  25. implementations. An attempt to install one of those packages may result
  26. in blockers requiring the user changes the global USE=libav state.
  27. Please do not alter the state of 'libav' flag on a per-package basis
  28. (e.g. via package.use). The flag needs to be set globally to have
  29. consistent value throughout all packages. Otherwise, blockers will
  30. prevent upgrades.
  31. 2015-04-16-ffmpeg-default
  32. Title FFmpeg default
  33. Author Ben de Groot <yngwin@gentoo.org>
  34. Posted 2015-04-16
  35. Revision 1
  36. Since the choice between ffmpeg and libav has been made more
  37. explicit, there has been a lot of discussion about what the
  38. default implementation should be. It can be concluded that
  39. media-video/ffmpeg has wider support, and would be somewhat
  40. more convenient for most end-users.
  41. For this reason the default implementation has been switched
  42. back from media-video/libav to media-video/ffmpeg by removing
  43. the libav useflag from the base profile.
  44. If the libav useflag is already globally enabled or disabled
  45. in /etc/portage/make.conf, then no further action is required.
  46. Users who implicitly relied on libav being enabled in their
  47. profile, and who wish to continue using libav, should enable
  48. USE=libav in their /etc/portage/make.conf file.
  49.