You are not logged in.
I guess you can't comment on closed FS reports, so I figured I would get more opinions instead of re-opening the bug just to make comments.
I can understand that gui deps should be optional (in fact, I don't even use the gui parts myself). The problem is that I've never used mkvextract without using mkvinfo first, and mkvinfo won't even give cli output without wxgtk libs.
Does anyone actually run mkvextract without running mkvinfo first? If so, how do you get the track/codec info?
If the general consensus is that mkvextract and mkvinfo indeed go hand-in-hand, then I'll re-open the FS report since mkvinfo requires wxgtk even if you just use it for cli output. If it gets closed again, it's not a big deal. I only noticed it when I cleaned up some orphan deps today, and it just seemed a little odd to me ![]()
Last edited by tdy (2009-12-28 03:55:30)
Offline
Well you can always re-build it yourself using abs without the gui and such. There is a neat gui for mkvextract on windows, doesn't seem to exist on linux though.
Offline
how do you get the track/codec info?
mkvmerge -i file.mkv
Offline
mediainfo is a helpful tool to expose detailed info out of a wide range of formats of media files, including matroska. You can find it in AUR.
This silver ladybug at line 28...
Offline
mkvmerge -i file.mkv
exactly what i'm looking for! thanks.
Offline