On mer, apr 29, 2015 at 02:29:43 +0200, Bálint Réczey wrote: > > Since there are concerns on shipping both libav and ffmpeg, we won't allow > > ffmpeg unless it is chosen to be the default and there is a clear transition > > plan, so that we can switch from one to the other. Only then will the block hint > > be removed. > There are no technical reasons for not having both in testing an I see > this the only fair solution. There are no name- nor symbol collision > between the packages. They co-exist perfectly on my systems, too. There is at least one reason that I can think of. Assuming the decision to keep either libav or ffmpeg (not both) stands, if ffmpeg is allowed to migrate and other packages start depending on it, and if before the stretch release ffmpeg is deemed not release ready (e.g. if libav is chosen), then more work will be required to untangle the dependencies and have ffmpeg removed from testing. Cheers
Attachment:
signature.asc
Description: Digital signature