> I'm not sure what you consider the "normal places". The myhtv manual > builds result in the binaries, etc. being placed into /usr/local/bin. > Most rpm or ebuilds I've seen place the binaries, etc. into /usr/bin. > > I've seen several ebuilds floating around. Search this list to find > examples. I believe the ebuild available at > http://bugs.gentoo.org/show_bug.cgi?id=66337 is the one that most > gentoo users are using. > > I took a whack at creating my own ebuilds based on the work above, > which better fits my needs. Here are my ebuilds if you want to play > with them: > > http://threeputt.org/ebuilds/mythtv-0.17_pre.ebuild > http://threeputt.org/ebuilds/mythtv-plugins-0.17_pre.ebuild > http://threeputt.org/ebuilds/mythweb-0.17_pre.ebuild > > I run a combined frontend/backend system, so my preference was to have > as few ebuilds as possible, so the mythtv ebuild has what people > normally break up into backend/frontend builds and the mythtv-plugins > has all of the standard myth plugins, plus nuvexport. The mythweb > ebuild, obviously only has the mythweb stuff... :) > > These ebuilds are a work in progress, so if you find any problems, I'd > appreciate you letting me know. > The ebulds that are available are doing the right thing. I am looking for language support in the ebuilds, but can 't find it, nor the cvs-ebuilds nor the ebuilds from portage. Someone knows more about this? peter
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
