The ebuild of enemy-territory downloads version 2.55 of the game, and after that it downloads and installs the update to current version 2.56. Is there a possibility to alter the ebuild a little so that it tries to download version 2.56 instead of patching it? Or that if 2.56 is already in distfiles, it will just take this file? Thanks in advance. Reproducible: Always Steps to Reproduce: 1. emerge enemy-territory 2. 3.
Can you give me a good reason why I should require people to download another ~300MB when all they need is the update? The end product is the same either way. The user gets a current version of the game. When the ET ebuilds were created there wasn't even a full download for 2.56, only the update. I'll have to let this get discussed among the games team and we'll make a decisionon what to do here. If you really want this quickly, I would suggest you hack up the ebuild and make the necessary changes yourself and post it here. It might make for a quicker uptake, plus you can use the ebuild in your overlay to install from so you'll be happy also.
2.55 + 2.56 update was the best course of action for anybody who already had 2.55 emerged ... the update was quite painless ... for people who are emerging 2.56 for the first time, they get a little extra overhead but not enough to warrant this change ... this is a known limitation of portage (not being able to have the option of patching to the current version or just using the current version) ... in other words, the current status is acceptable for most people and wont change until portage has an update
How about making 2 ebuilds of it. One with the latest game, and the other ebuild with update (enemy-territory.ebuild & enemy-territory-update.ebuild). I wish I could code some, but unfortunately I'm just an ordinary sucker ;-)
quote from Chris "Can you give me a good reason why I should require people to download another ~300MB when all they need is the update?" If you got an old version, there could be an alternative update ebuild. It would be stupid indeed to download another 300MB. But it's also stupid that when you don't have the game yet, you see it downloads an old version.
the answer is 'no' until portage supports this we arent forking the packages
Okay, lets just hope Portage will support this very soon then.
First off, an "update" ebuild would not work. Portage just doesn't work that way, and probably never will. There would be no way to track what version was actually installed. Honestly, this is totally a cosmetic thing and probably not something I would ever worry about trying to fix. All that really matters is this... Is the end result the same? (ET 2.56) Well, it is the same. How we get there is inconsequential in the grand scheme of things.
