Hi everyone, Sorry if this got a bit long.. It did not start out that way, but..
I am new to the list, but not new to Linux and after 30 years whacking on code and installation issues I think I have some comfort level in doing most package installations. I have been lurking here for about 2 weeks now just looking over the issues with the Myth installation stuff trying to see what people are having problems with and such as I just started the install or .17 on my FC3 box.. I havve to agree that a "release" should be pretty damn stable and one of the most frustrating things in the world is when a released package "Should work", but does not and may never really work right (if at all in so many cases) because it is just slapped out never really tested. If a package is nothing more than alpha/beta/cvs code it probably should not be called a "release". Call it what it is.. developmental. What we are all trying to do is encourage others to switch to Linux.. Make a showing that what we can offer in the Linux community is QUALITY SOFTWARE. Make it work the first time around.. If a feature is not ready.. make it known that it is not support at the time of the release. MythTV is really looking nice and the direction it is going is very promising.. but I have made three attempts to install and make this work on 2 different systems (FC2 & 3) that have complete video editing systems on them (Kino & Transcode) plus a huge amount of other similar type packages and they are all working very well.. I can not for the life of me make MythTV work on the FC2 box. I am beging to get it working now on the FC3 box but during liveTV the sound is arriving about 400-500 ms before the video and there is no sound on a recording (Hauppauge WinTV/VIA sound onboard). I know there is a solution, but Mr. & Mrs. avg Joe/Betty user don't want to fight with this kind of thing.. they can't.. They want to just install the package and go. This is exactly the area where we always loose to MS no matter how cool or powerful the software is. The struggles and hassles involed with dependancies in the *NIX world are staggering. Having to uninstall old libraies and reinstall new ones and recompile tons of code to make something works is truely rediculous if one stops to think about it. The simple fact that a released RPM/DEB/WHATEVER just does not install and run is what is killing us at the desktop in the NIX vs MS war. Rant and rave all you want about stupid MS & MAC users should learn to use a computer, it does not matter.. they are right. A package should just install and work with a minimal of hassles. If you took you car to a dealer for tires and they told you that you also had to upgrade the chip in the fuel management computer or the tires would not work, and in order to update the chip the transmission had to be upgraded too, and to do that the wiper blades had to be updated. But after the wiper update the headlights won't work.. what would you say?? What would you do? Onto the issue at hand. I think that a solution to this database issue is to have a repair/fix function that would create a dummy file (touch) and then allow a forced deltion of the data. And it should be from within the program so that there is no need for a command line.. After all if this is a set-top box, where is your command line? Just my thoughts. Keep up the good work.. it is needed and much appreciated. -R Bruce Smith reportedly babbled: >> > If the answer is always "use CVS" then why is there a >> > release at all? >> >> Good question. After all, releases just encourage people who don't >> contribute anything to the project to bitch and whine about how the >> devs aren't doing thing the right way. > > The problem with that statement is not everyone can be a MythTV > developer, even if they have the programming experience required. > Do you expect EVERYONE, including Linus, to drop what they are > working on and turn their attention to Myth? I'm sure you'd like that, > but in the long run it's probably not a good thing. :-) > > I am an unpaid core developer on a Linux distribution, so I contribute > my time to Open Source, just not the Myth project. > > I LOVE Myth, and have been running it since 0.14, but like others I > wish the official releases were a little more stable. > > Myth is something I want to work reasonably well so I can spend my > time doing other open source development. I really don't want to > spend my time with CVS and compiling Myth. I just want to download > the binary packages and use it. > > You guys probably wouldn't like it if NO Linux distributions were > stable and you had to compile the entire distro from CVS to get > a stable platform to run Myth. > > I realize it's difficult for the developers to find bugs without a lot of > people testing the product. So, perhaps a pre-release would be a > good idea so people can find bugs before an official release comes > out? Or always release a X.XXa release a couple weeks after each > official release to clean up new problems? (same difference) > > I'm trying not to be critical, but only want to offer suggestions to make > Myth a better (and more stable) product for everyone. Keep up the > good work! I love my Myth box!!! > > - BS > _______________________________________________ > mythtv-users mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > -R -- ------------------------------------------------------------------------ Rich Hall [EMAIL PROTECTED] http://www.netlynx.us/rich/ ham radio: kf6arx ------------------------------------------------------------------------ No trees were destroyed in the sending of this message; however, a significant number of electrons were terribly inconvenienced. ------------------------------------------------------------------------ And remember - if it ain't broke, hit it again. _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
