public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: USE=libav as replacement for broken || ( libav:= ffmpeg:= )
Date: Mon, 19 Jan 2015 23:44:48 +0100	[thread overview]
Message-ID: <1421707488.1239.3.camel@gentoo.org> (raw)
In-Reply-To: <20150119234044.7db04287@pomiot.lan>

El lun, 19-01-2015 a las 23:40 +0100, Michał Górny escribió:
> Dnia 2015-01-19, o godz. 23:09:55
> Rémi Cardona <remi@gentoo.org> napisał(a):
> 
> > Why not :
> > 
> > libav? ( media-libs/libav:= )
> > ffmpeg? ( media-libs/ffmpeg:= )
> > 
> > + REQUIRED_USE="^^ ( libav ffmpeg )"
> > 
> > I for one would never expect USE=-libav to enable ffmpeg (nor
> > USE=-ffmpeg to enable libav FWIW).
> 
> Two reasons:
> 
> 1. Compatibility. USE=ffmpeg is already used for || ( libav ffmpeg ) in
> a lot of packages. If we changed the meaning, libav users will end up
> switching '-ffmpeg libav' per-package. Ugly.
> 
> 2. Feature-oriented flags. USE=ffmpeg represents the generic feature,
> USE=libav is auxiliary implementation-switch flag. Well, maybe we could
> use, say, USE=avcodec to avoid ambiguity but that's a larger change.
> 
> 

I agree with your suggestion but I would prefer the Remi's approach of
letting people to know if they want "ffmpeg" or "libav", otherwise it is
not so obvious to know what disabling/enabling one of that USE flags
will end up causing without reading each ebuild :/ (also, maybe some
ebuilds will use one logic while others the inverse)



  reply	other threads:[~2015-01-19 22:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 19:31 [gentoo-dev] RFC: USE=libav as replacement for broken || ( libav:= ffmpeg:= ) Michał Górny
2015-01-19 19:36 ` Matthias Maier
2015-01-19 22:09 ` Rémi Cardona
2015-01-19 22:40   ` Michał Górny
2015-01-19 22:44     ` Pacho Ramos [this message]
2015-01-20  2:07       ` Michael Orlitzky
2015-01-20 10:31         ` Luca Barbato
2015-01-20 16:22           ` Michael Orlitzky
2015-01-20  0:10     ` Gordon Pettey
2015-01-20  7:36     ` Rémi Cardona
2015-01-20  7:39       ` Michał Górny
2015-01-20  4:44 ` Jason Zaman
2015-01-20  8:13 ` Alexis Ballier
2015-01-20  9:01   ` Zac Medico
2015-01-20  9:11     ` Alexis Ballier
2015-01-20 17:28       ` Zac Medico
2015-01-20 18:20         ` Alexis Ballier
2015-01-20 18:33           ` Zac Medico
2015-01-21 10:21             ` Alexis Ballier
2015-01-20 17:24   ` Ciaran McCreesh
2015-01-20 21:43   ` Michał Górny
2015-01-21 10:05     ` Alexis Ballier
2015-01-21 10:15       ` Michał Górny
2015-01-21 11:12         ` Alexis Ballier
2015-01-21 18:21           ` Michał Górny
2015-01-22  7:25             ` Alexis Ballier
2015-01-22 10:50               ` Zac Medico
2015-01-22 11:11                 ` Alexis Ballier
2015-01-22 17:06                   ` Zac Medico
2015-01-23  9:48                     ` Alexis Ballier
2015-01-23 17:19                       ` Zac Medico
2015-01-26 11:57                         ` Alexis Ballier
2015-01-26 15:26                           ` Michał Górny
2015-01-26 19:49                           ` Zac Medico

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1421707488.1239.3.camel@gentoo.org \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox