On Wed, 14 March, 2007 12:10 am, Lucian Muresan wrote: > Duncan Webb wrote: > >> On Mon, 12 March, 2007 9:54 am, Dirk Meyer wrote: >> >>> "Duncan Webb" wrote: >>> > [...] > >>>> There are some dependencies that could be a problem, Python-2.5 and >>>> Twisted-2.5.0. For Python-2.5 to work it will require, the soon to >>>> be released kaa-imlib2-0.2.1.tar.gz package. Also >>>> kaa-metadata-0.6.1.tar.gz and kaa-base-0.1.3.tar.gz will be released >>>> too. Twisted-2.5.0 will not work with out a patch. >>> Does the ebuild need 2.5? I don't see it. And does Freevo 1.7 need >>> it? >> >> No but when ~x86 is defined then it pulls in Twisted-2.5.0 so the >> ebuild needs a "<Twisted-2.5.0" > > The "~86" keyword should never be defined globally, anyway, but only > individually on a per package basis in /etc/portage/packages.keywords, that > way, if defined for freevo only, this does not necessarily mean that > twisted-2.5.0 or python-2.5 is pulled. I still have twisted-2.0.1 and > python-2.4.3-r4 on my system, and will most certainly upgrade python when > there is no other way to run a certain package, or use certain features of > a package...
I agree with all of this. The problem comes when someone has defined ~x86 or ~amd64 in the /etc/portage/package.keywords file for the twisted pacakge, then they will pick up Twisted-2.5.0 which doesn't yet work with freevo-1.7. So if the <Twisted-2.5.0 dep is in the freevo module then the Twisted package will be "downgraded" to Twisted-2.4.0. For the AMD64 processors Python-2.5 doesn't work, it seems that there is a problem with Python-2.5 and pygame-1.7, which means that the pygame ebuild should also check this but this may be out of your control so it could go into the freevo ebuild. > Speaking of the keywords, shouldn't the ebuilds in the freevo overlay > have different keywords? This might be regarded differently by an official > gentoo package maintainer, but in this overlay, as it's for "early > adopter" freevo users, I think that snapshots should be marked unstable > with "~x86", the released versions stable "x86" (also the same for other > architectures, if tested) which would leave room to be able to choose > which of them to use, by just changing the keyword for the respective > package in /etc/portage/packages.keywords. This would even work if we'll > have svn ebuilds pulling the latest version (as ebuild version, as you > know, they would be 9999) and they would typically carry the "*-" keyword. Yes, this is the normal gentoo logic. Doesn't "*-" mean that you need to add the package to the /etc/portage/packages.unmask file? > I know, something similar can be achieved by the mask/unmaks files, but > that would mean one have to run after every version, adjust it in that > file, while the keyword variant, if kept in that scheme, would always get > stable/unstable/testing versions of the packages to those who chose the > respective keywords for the respective packages, in the newest available > version in that category, whithout having to adjust versions in the > mask/unmask files. I have to quite often add package versions to /etc/portage/packages.mask even when they are marked as stable. Duncan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
