This is a request for an ebuild for the xvid media library, used by transcode to encode video, and possibly needed by xine to play video. I could try to make this ebuild myself, but it seems like something that could be tied to a 'xvid' use variable, so I figured I'd leave this to the professionals. If there is a better way to make ebuild requests, please let me know.
Please create one and attach it to this bug report.
Created attachment 1695 [details] xvid snapshot ebuild xvid ebuild
here's an ebuild for xvid snapshot 20020412. It does not have a configure script, and I don't know how to patch the makefile to use make.conf flag settings, so right now it has it's own CFLAGS. I will try to update it when I find out how to do this.
Created attachment 1727 [details] xvid snapshot r1 new r1 xvid ebuild to use patch for make.conf CFLAGS
Created attachment 1728 [details] makefile patch makefile patch to use make.conf CFLAGS
During the xine-lib configure process, it looks for xvid support, and unless xvid.h is in /usr/include, it says xvid support is disabled. This ebuild will install xvid.h, so maybe xvid could also be added to xine-lib and anything else that can use it, maybe under the avi use variable
Created attachment 1734 [details] new makefile patch new makefile patch to comment out CC declaration. Also, the default makefile is for x86 linux. sometime I'll try to figure out how to use the different arch makefiles
Created attachment 2150 [details] Changelog Here's the changelog, when will this be added to portage, and is there anything else I need to do?
Created attachment 2632 [details] xvid-20020412 updated for docs. Makefile patch no longer needed, used sed in ebuild to correct Makefile. Not tested on ppc and sparc so it may not compile, but should select correct arch Makefile to sed and make from.
Created attachment 2982 [details] xvid-20020810.ebuild Here's an ebuild for xvid cvs snapshots. 20020810 seemed to be fairly stable for me. One problem with this, though is that the SRC_URI is xvid_latest.tar.gz and not the snapshot date. I just thought I'd put this up there though, and maybe someone could put the actual snapshot with the date as part of the name on ibiblio or something, whatever.
Created attachment 3342 [details] xvid-20020822.ebuild This ebuild is for a named, downloadable snapshot, and works fine on x86. It _should_ work for ppc and sparc, but I can't test it on them right now. This should be used instead of previous ebuild posts.
I've installed this, and it works fine, the only problem is that to compile xvid support into mplayer libxvidcore.a needs to be copied as well. One other problem (for mplayer) is that it needs divx4.h, which copying that to /usr/include seems to break opendivx and divx5linux. (luckily I use libavcodec which supports divx4 and divx5)
Created attachment 4289 [details] xvid-20020822.ebuild Installs libxvidcore.a, hope this will work for mplayer. xvid probably shouldn't be used for divx support, that's what opendivx is for.
*** Bug 9708 has been marked as a duplicate of this bug. ***
I didn't know there is a xvid ebuild posted so I submitted bug #9708. I now see this one, and decided to anyway submit my ebuild here. I edited xvid-20020822.ebuild and adjusted it to mine, so as to not break anything that you were up to. Key differences in the ebuild I submit: 1. It uses cvs, no SRC_URI or similar 2. Instead of grepping ${CHOST} I changed it to "use x86", "use sparc" ... etc 3. Added dependency ">=dev-lang/nasm-0.98.30"... the xvid guys say it is required for building. Nothing else to it I guess. N.B. I also included the header that is known to break stuff - divx4.h... mostly because this is the ebuild I use at home. I also include encoder.h and decoder.h because I think mplayer need these four headers to detect xvid when compiling. Just change as appropriate afterwards. Hope the suggestions are welcome.
Created attachment 5122 [details] xvid-cvs-20021028.ebuild a cvs build for xvid (based on xvid-20020822.ebuild)
Added xvid-0.9.0.ebuild to cvs, thanks.
Just a quickie, what is the proper behavior that the xvid-cvs ebuild should have, since it provides the same functionality as the xvid ebuild. Does it have to `PROVIDE="media-libs/xvid"' or similar, in case a package needs xvid?
Sorda, yes, but official policy will hold that there will be no more (unless there is a *very* good reason) CVS ebuild in portage. Putting it more clearly: 1) CVS ebuilds rever to ones that use the cvs.eclass, and thus do not use a stable tarball that contain a snapshot of cvs tree. 2) Any dev that feel he have the spare time to maintain something like this, should only host on his homepage with clear notice that its not officially supported by Gentoo Linux. 3) Stable CVS snapshots (meaning creating a tarball from cvs, uploading to ibiblio, etc ...) will be allowed if it fixes bugs/compile problems with some or other version of gcc.
