This has already played out before..
Who remembers Netrek?
There were several clients to choose from to play the game. The trick? On major servers, you just had to use a blessed binary. Special permission to use RSA, and have developers responsible massivly cut down on ``borgs''.
If a developer was found to be producing clients that cheat, his key was yanked from the master server that all the game servers fed off of, and it revoked every client in the field.
Go Team Beer!
As evidenced by the messages already posted, the Dynamic/Static debate is probably going to rage on here.
To see how this will likely all play out, take a look at the NetBSD mailing list archives regarding the Pro's and Con's. You'll also see some of the solutions that came up to the various issues.
NetBSD has already gone through this flame war when they commited a dynamic root to their tree.
(Noted buried in one of the threads.)
This has already played out before..
Who remembers Netrek?
There were several clients to choose from to play the game. The trick? On major servers, you just had to use a blessed binary. Special permission to use RSA, and have developers responsible massivly cut down on ``borgs''.
If a developer was found to be producing clients that cheat, his key was yanked from the master server that all the game servers fed off of, and it revoked every client in the field.
Go Team Beer!
Actually, the number is 40+.
(As of this writing, there are 40 arches in the automated build loop, amd64 has not yet been added to the autobuild.)
As evidenced by the messages already posted, the Dynamic/Static debate is probably going to rage on here. To see how this will likely all play out, take a look at the NetBSD mailing list archives regarding the Pro's and Con's. You'll also see some of the solutions that came up to the various issues. NetBSD has already gone through this flame war when they commited a dynamic root to their tree. (Noted buried in one of the threads.)