public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Samuli Suominen <ssuominen@gentoo.org>
Subject: Re: [gentoo-dev] Re: virtual/ffmpeg and media-video/libav
Date: Mon, 28 Mar 2011 23:12:49 -0300	[thread overview]
Message-ID: <201103282312.49730.aballier@gentoo.org> (raw)
In-Reply-To: <4D8A0274.4000103@gentoo.org>

On Wednesday, March 23, 2011 11:23:48 AM Samuli Suominen wrote:
> On 03/23/2011 04:08 PM, Tomáš Chvátal wrote:
> > Hi guys,
> > As there is new ffmpeg fork that is a bit alive we should provide it as
> > alternative to current media-video/ffmpeg.
> > 
> > So libav is stored in media-video/libav (look at it, try to find issues
> > and stuff).
> > 
> > Virtual package is virtual/ffmpeg where now i implemented it to have
> > versioned dependencies.
> > So there is virtual/ffmpeg-0.6 virtual/ffmpeg-9999 where the apps can
> > decide what they need.
> > Samuli pointed out that we do not slot ffmpeg nor support versioned deps
> > and always demand everything to be working with latest. If you have
> > strong opinion on that one please express it here so the virtual gets
> > redesigned to just simple virtual/ffmpeg-0.1 without any version stated
> > in it. I myself like the chance to express the version explicitly.
> > Virtual itself provide access to all useflags currently used in eapi2
> > deps. More can be added when required.
> 
> With the same logic we have always pulled in from master, instead of
> release trees (such as 0.5.x, 0.6.x).
> It's not legal to set versioned deps forcing downgrade on same
> stabilization level (stable, or ~arch) as that will just cause
> dependency conflict. Applies to any package.
> So just punt the just committed virtuals and just leave
> virtual/ffmpeg-0.ebuild.  Anything that doesn't work with latest and is
> not fixed in reasonable time, gets lastrited like before.


well, if you want to convert all the tree you'll need a versioned virtual 
because the >= deps are still needed
(and the virtual should also have >= deps, not ~ nor =..* in order not to 
force a downgrade because of an outdated virtual)

A.



  reply	other threads:[~2011-03-29  2:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 14:08 [gentoo-dev] virtual/ffmpeg and media-video/libav Tomáš Chvátal
2011-03-23 14:23 ` [gentoo-dev] " Samuli Suominen
2011-03-29  2:12   ` Alexis Ballier [this message]
2011-03-29 12:59     ` Tomáš Chvátal
2011-03-29 14:05       ` Alexis Ballier
2011-03-29 14:28         ` Tomáš Chvátal
2011-03-31  7:37         ` Tomáš Chvátal
2011-04-02 10:02           ` "Paweł Hajdan, Jr."
2011-04-02 19:41             ` Alexis Ballier
2011-04-02 20:04               ` Christoph Mende
2011-04-03 19:46               ` Mike Gilbert
2011-03-23 15:01 ` [gentoo-dev] " Jeremy Olexa
2011-03-23 15:10   ` Mike Frysinger
2011-03-23 16:24     ` Donnie Berkholz
2011-03-23 15:17   ` Tomáš Chvátal
2011-03-23 15:30     ` Luca Barbato
2011-03-28 11:26 ` Tomáš Chvátal
2011-03-30 12:50   ` Alexis Ballier
2011-03-29  2:25 ` Alexis Ballier
2011-03-29  7:26   ` 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=201103282312.49730.aballier@gentoo.org \
    --to=aballier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ssuominen@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