I wrote the kaa ebuilds from scratch (they aren't in portage yet), but the freevo ebuild is based on the portage version (1.6.0). Please double-check the src_install() part
Created attachment 102905 [details] media-tv/freevo-1.7.0_rc1.ebuild
Created attachment 102906 [details] dev-python/kaa-base-0.1.1.ebuild
Created attachment 102907 [details] dev-python/kaa-metadata-0.5.ebuild
Created attachment 103127 [details] freevo-1.7.0_rc1.ebuild reworked Reworked the ebuild. Commented out some of the files that are no longer part of the distribution. Added some more setup options for directfb and matrox.
Created attachment 103128 [details] kaa-base-0.1.1.ebuild reworked Added dependency to glibc-2.4. See freevo mailinglist
If you emerge freevo-1.7_rc1 and unmerge mmpython you will get the following error: Error: VIDEO_SHOW_DATA_DIR not found Error: Installed mmpython version is too old. Please update mmpython to version 0.4.3 or higher This is because my python can not handle statements like the following: import kaa.metadata as mmpython import mmpython.version This statement will not work but is used in freevo/main.py. I havent found this to be an error as the import statement should work this way. Trying to to this in the python console gives the following: >>> import kaa.metadata as mmpython >>> import mmpython.version Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named mmpython.version >>> import kaa.metadata.version As you see kaa.metadata.version exists but is not accesable through the mmpython namespace. I have no clue as to why this is so. My emerge --info: Portage 2.1.1-r2 (selinux/x86/2006.1, gcc-4.1.1, glibc-2.4-r4, 2.6.18-hardened-r1 i686) ================================================================= System uname: 2.6.18-hardened-r1 i686 AMD Duron(tm) Processor Gentoo Base System version 1.12.6 Last Sync: Fri, 01 Dec 2006 13:30:01 +0000 app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r4 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -mtune=athlon -march=athlon -fomit-frame-pointer -fforce-addr -pipe -fstack-protector -fPIC -mmmx -m3dnow" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O3 -mtune=athlon -march=athlon -fomit-frame-pointer -fforce-addr -pipe -fstack-protector -fPIC -mmmx -m3dnow" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks loadpolicy metadata-transfer sandbox selinux sesandbox sfperms strict" GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo/ http://ftp.gentoo.or.kr/ http://ftp.du.se/pub/os/gentoo" LANG="en_US.utf8" LC_ALL="en_US.utf8" LINGUAS="en de" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X a52 aac acpi alsa amd amr apache2 apm asf async bash-completion bcmath berkdb bidi bzip2 calendar caps cdb cddb cdparanoia cdr chroot cli contentcache cpdflib crypt css ctype cups curl curlwrappers dbase dbm dga dio directfb divx4linux dri dts dv dvd dvdr dvdread elibc_glibc encode evo exif expat ext-zlib fam fame fastbuild fbcon fdftk ffmpeg filepro flac flatfile foomaticdb fortran fritzcapi_cards_fcpci ftp fusion gcj gd gdbm geoip gif gmp hal hardened hardenedphp iconv imagemagick imap imlib inifile inline innodb inode input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdn ithreads java jce jpeg kde kernel_linux ldap libedit linguas_de linguas_en lirc lirc_devices_sir live logrotate lzo maildir matrox mcal memlimit mhash mime mmx mp3 mp4 mpeg mpeg4 mplayer mtp musepack musicbrainz mysql mysqli mythtv ncurses nfs nls nocardbus nptl nptlonly ogg opengl pam pcntl pcre pdo pear perl pic png posix ppds prelude python qt3 qt4 quicktime readline real reflection samba sasl sblive scanner sdl selinux session sguil shared sharedext sharedmem snortsam soap sockets spamassassin spl sqlite ssl sysfs tcltk tcpd theora threads tidy tiff tokenizer truetype udev unicode usb userland_GNU userlocales utf8 v4l v4l2 video_cards_fbdev video_cards_matrox video_cards_mga video_cards_vesa visualization vorbis wddx win32codecs xanim xine xinerama xml xmlreader xmlrpc xmlwriter xorg xsl xv xvid xvmc zip zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Since 02 Jan there is Freevo-1.7.0-rc2. Has anyone written a new ebuild? Or can I change the version number and everything is ok? Tobi
I changed the ebuilds for rc2 as the final should be out within the next week
Created attachment 110904 [details] freevo-1.7.0_rc2.ebuild Freevo 1.7.0 rc2 ebuild. Added some more dependencies
Created attachment 110906 [details] kaa-base-0.1.2.ebuild Just a version bump
Created attachment 110907 [details] kaa-metadata-0.6.0.ebuild Another version bump. Changed deps to kaa-base-0.1.2
Created attachment 110908 [details] kaa-imlib2-0.2.0.ebuild Kaa-imlib2 is a new dependency for freevo-1.7.0_rc2
Freevo 1.7.0 final has been relased. Quote from their mailinglist (part of interest): "Today (25-02-2007), freevo-1.7.0 has been released, there has been a great deal of activity since freevo-1.7.0-rc2 with still more exciting new features. [cut] There has been no significant changes to the kaa modules that affect the operation of freevo-1.7.0 since RC2 (Release Candidate 2)"
Just a note, bug #163052 still present in version 1.7.0 ,twisted-2.5 not compatible....
Created attachment 111262 [details] dev-python/kaa-imlib2-0.2.0-r1.ebuild * dev-python/kaa-imlib2-0.2.0-r1.ebuild I added a required dep: >=media-libs/imlib2-1.2.1 * I made all initial ebuilds obsoletes * For the latest 1.7.0 (final) version simply rename the _rc2 ebuild TODO: I think we need to clean up the freevo ebuild (some files doesn't exist anymore for example). I'll do this as soon as possible
Created attachment 111303 [details] dev-python/kaa-imlib2-0.2.0-r2.ebuild fix deps and cleanup
Created attachment 111305 [details] dev-python/kaa-base-0.1.2-r1.ebuild fix deps and cleanup (accordingly with http://freevo.sourceforge.net/cgi-bin/freevo-2.0/Kaa#head-98389a8c11a2b5fb9a270b112686cceb9e61c071)
Created attachment 111306 [details] dev-python/kaa-metadata-0.6.0-r1.ebuild fix deps and clean up accordingly with http://freevo.sourceforge.net/cgi-bin/freevo-2.0/Kaa#head-919960011a3523a465d1cacc57f2f8e7b0e8ad00
Created attachment 111308 [details] dev-python/pyNotifier-0.3.9.ebuild New ebuild, optional for kaa-base (see: http://freevo.sourceforge.net/cgi-bin/freevo-2.0/Kaa#head-98389a8c11a2b5fb9a270b112686cceb9e61c071 )
I added three new useflags to kaa-base ebuild: IUSE="kaa-db pynotifier lirc" I choose to add kaa-db because of its deps (glib and pysqlite). I'm not sure about the "names" feel free to suggest any other choice :)
Can we move this one a little bit, please? I'm waiting for the new features... :-(
There is no developer that is interested in maintaining freevo. It is currently unmaintained. Your best bet is to get this into Project Sunrise. Or if Frittella Laurento is willing to proxy maintain it (i.e. bugs get assigned to Frittella and I'll commit the fixes for Frittella) then that's an option.
(In reply to comment #22) > There is no developer that is interested in maintaining freevo. It is currently > unmaintained. Your best bet is to get this into Project Sunrise. Or if > Frittella Laurento is willing to proxy maintain it (i.e. bugs get assigned to > Frittella and I'll commit the fixes for Frittella) then that's an option. Ok, I will do it willingly... no problem here ;)
The same issue is still there, bug# 163052 that's not easy to solve and will be present till version 2.0.....
(In reply to comment #24) > The same issue is still there, bug# 163052 that's not easy to solve and > will be present till version 2.0..... > But that shouldn't keep 1.7.0 from being accepted to portage...
Created attachment 113714 [details] freevo-1.7.0-r1.ebuild Reworked freevo-1.7.0 ebuild to include a patch for imdb. Otherwise freevo 1.7 will crash when trying to get some information from imdb. We can also wait for the next release as this patch is included upstream. I would not suggest to include this release in portage without the patch.
Created attachment 113715 [details, diff] fxdimdb-genre.patch Patch to work with emtpy fields in imdb infos. See freevo bugtracker for details
...just tested the ebuilds and they all work fine on ~amd64. Please push to portage.
(in reply to comment #25) >But that shouldn't keep 1.7.0 from being accepted to portage... Eh.... committing it with dependancy like: ">=dev-python/twisted-2.0 <dev-python/twisted-2.5" would probably give a QA issue, so I can't imagine a way for committing freevo version 1.6.2 and 1.7.0 in portage,even if they're working. Ask twisted maintainer to mask 2.5.0? (I have no idea of what else depends on twisted....)
Created attachment 117166 [details] freevo-1.7.0-r1.ebuild This one fixes some bugs..... well: bug #163052 , by putting in the depend "=dev-python/twisted-2.4*" (is the stable one). bug #167893 by using sed on setup_freevo.py script and then using insinto as per usual ebuilds. bug #175607 by putting ${ROOT} before any /usr or /bin in the ebuild. please test.
Created attachment 117192 [details] freevo-1.7.0-r1.ebuild Better version of the above (added last ${ROOT} and moved sed line for setup after install so it doesn't change the installed freevo setup)
Created attachment 117369 [details] kaa-imlib2-0.2.0-r1.ebuild other ebuild's configure failed with error: couldn't find imlib2-1.2.1. Added use flag for media-libs/imlib2
I swear if this is the right way to insert in portage. I mean, all those kaa lib packages are unlikely to be used from any other packages, and grouping them in a single ebuild wouldn't be a big issue as emerging python stuffs is fast....
Freevo 1.7.1 is out. Renaming the ebuild didn't quite work, as the imdb patch wouldn't apply. However, looking at the changelog 1.7.1 contains several imdb fixes, so I suspect this patch is in now? I haven't been able to confirm. I got it to merge by commenting out the patch line in the ebuild, but haven't been able to check the imdb/fxd stuff. Current latest versions of deps are updated too: kaa-imlib2-0.2.1 kaa-metadata-0.6.1 kaa-base-0.1.3 Renaming the above ebuilds to the correct version numbers and re-merging appears to work.
Created attachment 118870 [details] freevo-1.7.1.ebuild Theese are the ebuilds for freevo-1.7.1, kaa-base-0.1.3, kaa-metadata-0.6.1 and kaa-imlib2-0.2.1. All works correctly as far as I tested. I added dvd and css useflags for kaa-metadata since it requires libdvdread and libdvdcss to be installed before it (see http://freevo.sourceforge.net/cgi-bin/doc/FAQ). I added xine-only use flag for freevo-1.7.1 to build xine instead of mplayer (it isn't recomended but nothing forbids it). Actually freevo developers recomend both to be installed and xine to be used for dvd playback; there is no strict necessity for mplayer. I read about Matteo Azzali's proposal to group all kaa ebuilds into one but I didn't since i'm no developer and it's none of my business to take such a decision.
Created attachment 118871 [details] kaa-base-0.1.3.ebuild
Created attachment 118873 [details] kaa-imlib2-0.2.1.ebuild
Created attachment 118875 [details] kaa-metadata-0.6.1.ebuild
Thank you everyone for being so helpful on this bug. I'd be willing to maintain this package (with any help you're willing to provide). I'd just like some feedback from some other devs on the local USE flags that would be added to the tree... Particularly, with respect to xine-only. Is this really necessary? Shouldn't freevo detect that mplayer is not available and default to xine in such an event? In this case, we could just drop the xine-only use flag and mplayer dependency altogether. I use freevo with mplayer, so can anyone who uses freevo without mplayer comment?
If you really want to have a xine / mplayer war, then just let them set one or the other in the use flags. if ( use xine && use mplayer); then eerror "Can only have use flag 'xine' or 'mplayer' set" fi Something like that. I'd prefer to let the user pick it though, and leave the use flags out completely.
Don't waste time with specifical mplayer/xine use flags, all should be configured through the freevo configuration files. Still the issue is that freevo 1.7 and much more the still not released 2.0 have a lot of libraries (needing to be accepted from dev-python and then keyworded),a convenient solution may be to create a single ebuild for all the libraries at once (freevo-libs?). I would suggest you to start adding 1.6.3 to portage (still stopped to 1.6.1), but be warned that both 1.6.3 and 1.7.1 seem to have weather plugin completely broken (that stopped myself from adding 1.6.3 to portage..)
(In reply to comment #41) > Don't waste time with specifical mplayer/xine use flags, all should be > configured through the freevo configuration files. Sounds good to me. (In reply to comment #41) > Still the issue is that freevo 1.7 and much more the still not released > 2.0 have a lot of libraries (needing to be accepted from dev-python and > then keyworded),a convenient solution may be to create a single ebuild > for all the libraries at once (freevo-libs?). I think not. Wouldn't that be completely against Gentoo policy/convention? If a package appears in portage, it appears under the same name and version (exempting -r releases) as what the vendor provides it under. The vendor(s) here are clearly providing four separate packages each with their own name and version; I think it a bad idea to combine them, slap our own name and version on them, and call it a day. To the python herd: what do you think? (In reply to comment #41) > I would suggest you to start adding 1.6.3 to portage (still stopped to > 1.6.1), but be warned that both 1.6.3 and 1.7.1 seem to have weather > plugin completely broken (that stopped myself from adding 1.6.3 to > portage..) I think that the weather plugin was fixed (at least for me) in 1.7.1.
Please note: there are 4 libs for freevo 1.7 and more than 8 for freevo 2.0... good luck in asking dev-python to insert all them and then archs to keyword, that's an hell to maintain and nobody else than freevo is gonna using those libs. For the weather plugin I know only what my freevo is givin me for europe locations: ERROR obtaining forecast data for 'IEXX0014' ERROR obtaining forecast data for 'ITXX0093'
(In reply to comment #39) > I'd just like some feedback from some other devs on the local USE flags that > would be added to the tree... Particularly, with respect to xine-only. Is this > really necessary? No it isn't necessary. Simply freevo uses mplayer, xine or both for audio, video and dvd playback (it can be configured in its config file). Since it happens to be frequently installed on small machines (like media-players and the like) it may be useful to cut some unnecessary dependencies to reduce compile time... Maybe it would be nice to have only a simple flag to remove both mplayer and xine as dependancies and add an ewarn to note that the user must install one of those players to play video/music in freevo. It may be useful also because freevo does not only plays video/music but may be used as a gaming platform too, so some user may not need any video player. This is only my poit of view obviously and not a major problem at all ;-)
Created attachment 120470 [details] freevo 1.7.2 bugfix relase Freevo 1.7.2 is out and should be a bugfix relase (see http://freevo.sourceforge.net/cgi-bin/doc/ChangeLog) I made a few minor changes: - removed libsdl dependency since it is already a pygame dependency - removed "encode" use flag (and related dependancies) since it controls some optional features that are mplayer (mencoder) features (it has already an "encode" flag) - added "minimal" use flag to remove mplayer dependency - added "tv" use flag to put into tvtime and xmltv wich are used by mplayer to watch tv (xmltv is a little optional and doesen't get installed with "minimal" use flag enabled). I couldn't find an existing use flag that did such a thing so I had to create a new one... sorry. - added "mixer" use flag to add aumixer dependency (it is used to control volume by mixer.py) - added "sqlite" use flag since freevo uses pysqlite for "freevo cache" which is optional I suppose (since I never used it). I didn't tested that feature though... Theese changes are those that I use on my system so they may be unfitting to go into portage
Note that for pysqlite support to work, pysqlite 1.x must be installed. (It's a SLOTed ebuild, and by default 2.x will be installed, which freevo doesn't recognise) I'm not sure how to update the ebuild to take account for this.
I noticed that the attached "kaa-imlib2-0.2.1.ebuild" depends on "dev-libs/libxml2" (my original ebuild doesn't) I think we should remove this because: kaa-imlib2 )--depon--> kaa-base )--depon--> libxml2
Created attachment 120609 [details] freevo-1.7.2-r1.ebuild with correct dependancies Corrected pysqlite dependency.
kaa-imlib2-0.2.1.ebuild depends on libpng. Of course most people have that, but I didn't trying to build a framebuffer media box from scratch.
/etc/init.d/freevo and /etc/conf.d/freevo have gotten lost at some point. They were in 1.5. (and worked very well)
(In reply to comment #49) > kaa-imlib2-0.2.1.ebuild depends on libpng. Of course most people have that, > but I didn't trying to build a framebuffer media box from scratch. kaa-imlib2 )--depson--> imlib2 )--depson--> libpng (if you compile imlib2 with "png" useflag) Where are you read kaa-imlib2 strictly deps on libpng? On the official website I haven't found it: http://freevo.sourceforge.net/cgi-bin/freevo-2.0/Kaa#head-c1c4010397b72bed2a999c08e08d702439c17512
(In reply to comment #50) I think they were removed for security reasons (see bug 150568)
Please note: mplayer package is required to use the recordserver, as analogic recording is done through mencoder.....
matteo: You gonna add this?
(In reply to comment #53) > Please note: mplayer package is required to use the recordserver, as > analogic recording is done through mencoder..... > Yes but the recordserver is an optional feature for those who doesn't use freevo to record something... Well it doesn't matter since most users will use mplayer in most cases.
Doug: I'm not the freevo maintainer, I tried to fix some bugs previously but I'm not actually interested in maintaining a package with so many dummy dependancies, if someone else has more time/patience than me he's welcome, otherwise I'll maybe add 1.6.3 version to portage just to get rid of some open bugs, no more.
*** Bug 184650 has been marked as a duplicate of this bug. ***
Hey -- is anyone on sunrise maintaining this currently? I'm interested in bumping up to v1.7.2.. I'll do it if nobody else is..
(In reply to comment #58) > Hey -- is anyone on sunrise maintaining this currently? I'm interested in > bumping up to v1.7.2.. I'll do it if nobody else is.. http://overlays.gentoo.org/proj/sunrise/browser/sunrise/media-tv I don't see it in sunrise, so I'd say have at it.
This is marked 'maintainer-needed' -- that means its maintained via sunrise, but committed directly to portage. And yeah, i'm going to try and get the 1.7.2 ebuilds into portage today.
(In reply to comment #60) > This is marked 'maintainer-needed' -- that means its maintained via sunrise, > but committed directly to portage. Well no, maintainer-needed ebuilds are *not* maintained by sunrise at all; and cannot be commited anywhere else but to portage-review branch (which cannot be checked-out via layman).
Right. Well anyhow, genstef and Jokey and I worked out that this one should probably be moved to sunrise. I've commited the new ebuild (for 1.7.2) there, as well as ebuilds for kaa-* dependencies. I believe the plan is to hard-mask freevo for removal from the portage tree and switch it to maintainer-wanted, but allow sunrise to overlap until it is removed.
media-tv herd fully supports the removal of freevo from the tree. None of us use it and we haven't been able to find any developers that do use and are willing to maintain it.
I'm getting the 1.7.2 ebuild into the tree and will proxy it for Ian. Also, the package joins the media-tv herd as by beandogs wish.
I found that freevo-team (officially) mantains a gentoo overlay! http://freevo.sourceforge.net/cgi-bin/freevo-2.0/InstallationGentoo
it only contains ebuilds for the beta version of the upcoming 2.0 (freevo-1.99) which is unstable. The stable branch is 1.7.2 and is not present in that overlay
Yes. the freevo overlay only contains 2.x. I'm currently working with upstream to clean up some things in those ebuilds.
And the ebuild for 1.7.2 is in portage-review waiting to be added to the tree.
(In reply to comment #68) > And the ebuild for 1.7.2 is in portage-review waiting to be added to the tree. It is going to get into the tree, but please give me some time to test it thoroughly. The ebuild is waiting for months now, three more days for QA won't hurt anyone. Ian, please delete them from portage-review as I'd like to commit my current local copy. Also, the overlay since recently is also accessible via `layman'.
Just by the way, they're planning on releasing 1.7.3 in around two weeks. Not saying it changes anything, just something for your radar screens. http://sourceforge.net/mailarchive/forum.php?thread_name=469101F8.6080802%40freevo.org&forum_name=freevo-devel
(In reply to comment #69) > Ian, please delete them from portage-review as I'd like to commit > my current local copy. No problem -- grab a copy though before i drop it, as i squashed at least one bug relating to dependencies in that version.
(In reply to comment #71) > (In reply to comment #69) > > Ian, please delete them from portage-review as I'd like to commit > > my current local copy. > > No problem -- grab a copy though before i drop it, as i squashed at least one > bug relating to dependencies in that version. > where's it at?
1.7.2 is in the tree now, with the kaa ebuilds as single packages. This will also ease the future freevo-2 transition. Bug #163052 was not fixed yet. Thanks to all you guys helping. Please test. I expect the ebuild to have some bugs, so please report back.
(In reply to comment #73) > 1.7.2 is in the tree now, with the kaa ebuilds as single packages. Good news :) The first thing I noticed: kaa-base has not the pyNotifier as optional dep. I don't really known if it's useful but... (I quote from the kaa wiki): Dependencies: pyNotifier (optional), PySQLite 2.2+ (optional, but required for kaa.db), glib (optional, but required for kaa.db), PyLIRC (optional) PS: the pyNotifier ebuild is already attached
# emerge -p freevo These are the packages that would be merged, in order: Calculating dependencies \ !!! Multiple versions within a single package slot have been !!! pulled into the dependency graph: ('ebuild', '/', 'dev-python/twisted-2.5.0', 'merge') pulled in by ('ebuild', '/', 'dev-python/twisted-web-0.7.0', 'merge') ('ebuild', '/', 'dev-python/twisted-2.4.0', 'merge') pulled in by ('ebuild', '/', 'media-tv/freevo-1.7.2', 'merge') Since only dev-python/twisted-web-0.6.0 depends on =dev-python/twisted-2.4* here my proposed patch: --- /usr/portage/media-tv/freevo/freevo-1.7.2.ebuild 2007-07-15 21:16:42.000000000 +0200 +++ freevo-1.7.2.ebuild 2007-07-16 13:34:51.000000000 +0200 @@ -18,7 +18,7 @@ >=dev-python/pyxml-0.8.2 >=dev-python/imaging-1.1.3 =dev-python/twisted-2.4* - >=dev-python/twisted-web-0.5.0-r1 + =dev-python/twisted-web-0.6* >=media-video/mplayer-0.92 >=media-libs/freetype-2.1.4 >=media-libs/libsdl-1.2.5
(In reply to comment #75) > here my proposed patch: > > --- /usr/portage/media-tv/freevo/freevo-1.7.2.ebuild 2007-07-15 > 21:16:42.000000000 +0200 > +++ freevo-1.7.2.ebuild 2007-07-16 13:34:51.000000000 +0200 > @@ -18,7 +18,7 @@ > >=dev-python/pyxml-0.8.2 > >=dev-python/imaging-1.1.3 > =dev-python/twisted-2.4* > - >=dev-python/twisted-web-0.5.0-r1 > + =dev-python/twisted-web-0.6* > >=media-video/mplayer-0.92 > >=media-libs/freetype-2.1.4 > >=media-libs/libsdl-1.2.5 > Fixed, thanks for spotting (this was also reported as bug #185591)
(In reply to comment #74) > The first thing I noticed: kaa-base has not the pyNotifier as optional dep. > I don't really known if it's useful but... I can only look into that later. Ian?
While I was working on this I couldn't find an ebuild for pyNotifier, so I cut that use flag out. However, from what I can tell, none of the dependencies added by the use flags are needed at build time anyways -- so if one wanted to use pyNotifier with this they could just install it. Also, i'm thinking it would be a good idea to start new bugs relating to kaa-* packages, to keep this one relating more to the freevo ebuild...?
The original kaa-base shipped the pynotifier files it needs, but they had dependancies not covered by the kaa-base ebuild. You'll find a new kaa-base ebuild in the tree now that rdepends on pynotifier and does not install its own pynotifier code. Thanks for everyone helping to finally fix this bug!
dev-python/pynotifier brings up a lot of dependancies! It brings up x11-libs/qt too! People that (like me) use freevo on a framebuffer have no use of such libraries and it is a big compilation problem on slow machines (like those used as mediaplayers). Since kaa-base works even without pynotifier could you add a flag like "minimal" to pull out pynotifier? I used freevo 1.7.2 since it was out so I'm pretty sure that kaa-base works even without pynotifier :-)
(In reply to comment #80) > dev-python/pynotifier brings up a lot of dependancies! It brings up x11-libs/qt > too! > People that (like me) use freevo on a framebuffer have no use of such libraries > and it is a big compilation problem on slow machines (like those used as > mediaplayers). > Since kaa-base works even without pynotifier could you add a flag like > "minimal" to pull out pynotifier? > I used freevo 1.7.2 since it was out so I'm pretty sure that kaa-base works > even without pynotifier :-) It never worked without pynotifier, kaa only shipped its own (minimal) copy of it. I just committed pynotifier-0.5.8-r1 that has qt4 and gtk use flags. I believe pynotifier works without USE="gtk", it definately works without USE="qt4". Sorry for the inconvenience.
thanks! :-) I was scared when, this morning, emerge tried to install qt on my small machine! I never noticed something wrong in freevo without pynotifier but maybe I was simply non using some feature requiring it. Only a curiosity: what is pynotifier required for?
(In reply to comment #82) > I never noticed something wrong in freevo without pynotifier but maybe I was > simply non using some feature requiring it. > Only a curiosity: what is pynotifier required for? There's nothing wrong with the way it was before, pynotifier was included in kaa-base. Also, it's not needed for freevo 1.7, but 2.0 needs it for the program main loop.
