DirectFB optionally depends on avifile... the ebuild specifically does a depend on avifile version 0.6.0 or greater. any version of avifile less than the non-existant 0.7.0 is masked out. emerge installed avifile 0.5.something to fulfill the dependency. i'm using portage 1.8.8-r1.
DirectFB indead relies on avifile 0.6.0 or greater, but the latest version in portage is 0.53.5-r1. Surely 53 > 6. So I'm flagging this as invalid
noo... 0.53 is older than 0.6, 0.6 is the latest development version. i dont know why it's named 0.53 and not 0.5.3, but in this case of versioning 53 is less than 6. quoting from the avifile page: Here are some old obsolete sources just in case you would be looking for this kind of code - otherwise don't bother and download 0.6 version avifile-0.53.5.tar.gz (830 kb) - latest stable but OBSOLETE release. (and it doesn't compile on modern distribution - so DO NOT BOTHER with bugreporting - simply download and use latest avifile-0.6) the latest version is named: avifile-0.6.0-20011220admin.tgz <b> and it still doesn't answer why ANY avifile was installed in the first place. ALL versions of avifile were masked out....... </b>
It does answer that question since all versions lower than 0.7.0 are masked. 0.53.5 is considered higher than that since as I said 53 > 7. This is not a portage issue or a problem with emerge since if it should pick up this particular version, it should have been named 0.5.3.5 or something like that. Please leave this closed and submit a new bug about the avifile package.
