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