"Triffid Hunter" wrote:
> On the same note, if your distro provides a broken transcode package
> (which is appariently common), that is also the responsibility of your
> distro's maintainers and not the author of dvd::rip.
Thanks, Triffid, for your statements which are basically true ;) But I
don't think Andreas wanted to blaim "the author" (hey, that's me ;) for
his installation problems.
The idea of a static dvd::rip package or distro is not uncommon. I
remember myself installing dvd::rip *from scratch* (including *all*
dependencies and their dependencies, even a recent Perl, Glib/Gtk+ and
Glib/Gtk Perl-bindings, transcode, codecs and stuff, just an X server
was presumed ;) on a very old SuSE 8.x one or two years ago on a system
of a friend of mine (for some reason he wasn't willing to upgrade to
Debian ;).
The problem is: this build was SuSE 8.x specific, and I doubt it will
run today on a recent distribution, so maintaining such a package is a
big task. Building everything in a static version not using *any* system
libraries comes indeed near to building your own Linux distribution (and
is more memory consuming, since no shared memory is used). I personally
wouldn't accept rebooting my workstation just for ripping a DVD. I know
many users which won't accept this as well, e.g. all those who told me:
"Yeah, now I don't need to reboot into Windows anymore..." ;)
So Triffid is right: probably it's more efficient to bug your
distro/dvd::rip/transcode package maintainer(s) to provide useful
packages.
On the other side: when you want to do such a thing, I'd try to support
you by answering questions and providing webspace for distribution of
your package. But I think *maintaining* this package will be much effort
(e.g. you should have a bunch of distros around to test it), so think
about what you're doing... ;)
Regards,
Joern
--
Think, before you code.
pgp9f1fgPHauI.pgp
Description: PGP signature
|