Hi Wesley, > I got the idea from here: > > > http://lists.opencastproject.org/pipermail/matterhorn-users/2012-March/002196.html > > where a guy named Tobias opined: > > "If you were a developer and about to commit code to the project, you > should indeed be worried and probably hold back your commit until all tests > pass. As an adopter though, skipping the tests should not be a problem." > > But yeah, passing all tests is a good thing. But if a build test fails, and > you are a mere mortal adopter, what do do? File a bug report?
That guy would have been me :-) The reasoning behind that sentence you are citing is that if you commit code, and there is a unit test failre, you need to fix your code first, then commit. Like this - at least in theory - nobody (including mere mortal adopters) should encounter downloading code from the repository that do not build. That being said, some of the tests may require thirdparty tools to be installed properly in order for tests to succeed, and as Greg mentions correctly, skipping the tests doesn't help and will only push the problem out towards runtime where these tools are required anyways. <snip/> > Tried a bunch of tricks from MacPorts documentation. nada. thought I had it > by manually installing an earlier released Portfile, but then the menu3p > script stomped all over it and I was back where I started. Filed a bug report > with the port developer. I recently switched to Homebrew for 3rd party tools installation which made everything 3rd party related *much* easier. If you want to give that a try, install Homebrew, then issue: brew install mediainfo brew install ffmpeg brew install tesseract brew install leptonica Done. Tobias _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
