Hey All, I'm responding again because I saw that I left Luke off of my original message and I cleaned up my steps a bit.
We talked about this on the irc channel, and several of us feel that you
don't need anything special in the ebuild at all, you can do this via
package.mask and a newsitem.
I suggest the following assuming that the older version will stop
working when the network is fully upgraded.
- Publish a newsitem explaining this issue.
- After the newsitem is published, Commit the newer version under
package.mask with the mask message being an explanation of the issue.
- at this point, if people want to opt in, they can unmask the newer
version and add it to package.accept_keywords.
- Once the network is upgraded, unmask the newer version (and you
might have to fast stable if the older version doesn't work).
- If I understand correctly, at this point, opting in isn't
optional since the network is upgraded, so if people don't want
to use the new algo they can't use bitcoin.
That will give everyone time to see the newsitem before the newer version hits.
It seems like this is the best you can do since upstream is doing a hard
switchover to the new algo.
William
signature.asc
Description: PGP signature
