- #Dvdfab 11 strip warnings how to
- #Dvdfab 11 strip warnings install
- #Dvdfab 11 strip warnings software
- #Dvdfab 11 strip warnings windows
If a package used a universal naming convention, like the actual names of the programs the developers named them, then a program could simply say "I want this, this, and this" and the manager would know what the hell they wanted and install it all easily. Thank you distro wars for giving everyone less freedom and making Linux suck more.īut why are dependencies a problem? The reason is because *those* packages are proprietary.
#Dvdfab 11 strip warnings software
Until Linux users are really free to choose what software to install no matter their distro, and the focus is shifted to making the default software work correctly for all Linux users, you sadly will have more freedom in some ways on a proprietary OS. Metapackages are fine, but fucking around with software names just so you can make your repository be proprietary is wrong. If they want to modify a program, they need to change it's name, but if it's simply distros having different package names then they need to fucking stop it. Distros should be offering the same exact software that you can get easily online. This is one of the many reasons Linux packaging standards are needed. If, however, it was an Ubuntu packaging naming issue, I completely blame proprietary Linux packaging for that. The newer VLC should have required the newer ffmpeg.
If the issue was an ffmpeg or VLC issue, then that would qualify as a dependency issue. It's nice to have more time for real life than to be spending time adjusting my tools. I no longer have to spend time trying to make sure the tools taht are supposed to help me are set up properly or if I'm using the right settings.
#Dvdfab 11 strip warnings how to
Until Ubuntu gets this straightened out, anyone using Intrepid or following versions will have trouble with video codecs, including ripping DVDs and, in my case, trying to read files from my HD camcorder that were easily readable in Ubuntu Hardy, but which nobody was quite sure how to read (or what settings to use) in Intrepid.Īfter wasting several days of my life on this issue, I gave up, ordered an iMac, and since switching, have spent more time doing what I want on my computer and less time at the computer overall.
The VLC people claim some of those codecs are not available under Ubuntu (even with extra repositories), but they're there - just with different names. I was on both mailing lists for a while (VLC, FFMpeg) and the latter admitted to changing the names but did have all the codecs available under Ubunut. While the VLC people blame Ubuntu on their mailing lists, it turns out that the FFMpeg library uses different names for some codes in their newer version - and on the latest Ubunut (Intrepid), that version of VLC doesn't use the newer names. In fact, most of the time it signals that the writer has decided that she doesn't need to logically justify her statements and is a good idea to subject them to more scrutiny. PS: Saying end of story does not, contrary to popular belief, actually mean that it's the end of the story. ) so the application devs would write in whatever they want and computer users could run in whatever they want - because that's what computers are for: not doing "computer stuff" but using computers to accomplish things. TL DR version: It would be a wonderful world if all the OSs have compatibility layers for all the APIs (JVM/JNI, Mono/CLR, GTK, QT, WIN32, Carbon, Cocoa.
In fact, I'm quite happy that some kind soul has decided to hide as much of that as possible from me so I can focus on getting my actual work done. I write multi-platform OpenGL and OpenSSL code, when I call SSL_check_private_key(ssl_ptr) or gluNewQuadric(), I don't care what lower-level function is called. You wouldn't say that QT creates a "fake" QT environment for applications like KDE so why would you say that WINE provides a "fake" WIN32 environment for DVDFab? The application doesn't care what's underneath the API that it sees, it only wants function calls to result in the documented behavior and is agnostic about the rest. There is no principled difference between running an application that's NIX-QT-KDE and one that's NIX-WIN32-DVDFab. KDE requires the QT APIs in the same fashion that DVDFab requires the WIN32 APIS. WINE is a set of libraries that provides a different API on which some other applications are built. QT is a set of libraries that provides a certain API on which applications are built. You are comparing things on two different levels of abstraction here.
#Dvdfab 11 strip warnings windows
QT doesn't need a whole bunch of wrappers and libraries to fake a windows environment, DVDFab does.
0 kommentar(er)
