Hey, Cedega 5.0 has renamed its components to cedega and cedega-engine (instead of point2play and cedega), in the past Portage used to have 2 separate ebuilds for each component, now we only have 1 ebuild for cedega while the engine is left without an ebuild, this is understandable because cedega-engine is installed from within the GUI, however I can no longer verify the hash of cedega-engine before installing it as I used to with previous versions, I always appreciate an additional security check, suppose Transgaming's servers where compromised for example. My suggestion is simple, just add cedega-engine-${PV}-local-update.i386.cpkg to the list of downloads, this way portage verifies the file hash, and does nothing with the file, later when emerging is finished, display a message to the user saying that they need to install cedega-engine from within the GUI, and point them to its location in /usr/portage/distfiles. You can go further and add a package specific USE flag for the additional check, set off by default, to maintain backward compatibility. Although I don't have experience in creating ebuilds, if the suggestion is welcome, I can try my hand at it. Thanks and keep up the great work!
err, this seems like a one off thing ... the cedega-engine-5.1.1-local-update.i386.cpkg is an update to be applied on top of the cedega-5.1 release ...
Oh I see, I changed status to INVALID, thank you.
