On 05/01/16 00:31, Irrwahn wrote:
On Sun, 3 Jan 2016 17:52:48 +0000 (UTC), Go Linux wrote:
Why are you merging the debian, backports and dmo repos? Is there a way to
separate them? I have rarely used backports and always downloaded what I need
from dmo when I first install and then disable it. dmo can really break things
if you're not careful.
...
(Note: I, for one, am so far fine with having the bpo
and dmo repos merged, since I have been using those for
quite some time, but mileage varies vastly, as we all
know.)
...
One more note: I have no evidence, it's really nothing
more than just a gut feeling, but I expect less breakage
to occur WRT dmo packages in the foreseeable future, since
Debian returned to distributing ffmpeg instead of the
libav fork (They did, didn't they?), and I am under the
impression that a lot of the breakage was due to
mismatches between those two.
I am not familiar with recent compatibility, I have not updated any audio
workstations for some time, they remain as is. working and never updated.
But there has been a sad and difficult history of incompatibilities and sudden
breakages using dmo when dmo library updates break non-dmo audio apps which have
been built against debian libraries.
The dmo libraries did not match the versions in debian, and this includes both
the time before libav and since. ffmeg did not have a regular release system,
dmo built more frequently and against more recent snapshots than the ones in debian.
If you only used audio from dmo it was generally ok, but they do not cover a lot
of audio needs.
Based on past experience mixing those repositories would definitely exclude
using devuan from any audio workstation, or any system which needed other than
standard desktop audio needs. It is probably mostly ok with desktop audio.
It will certainly mean I cannot use devuan in most machines I look after.
Simon
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
