Post 1.4 of course, but I might as well ask now. I've just made a working crypt(3) implementation of blowfish (based on crypt_blowfish for glibc-2.1.3), and controlling this through a USE flag would be desireable. There are two alternatives: 1) Making blowfish default. I doubt this is any good, as it's fairly non-standard and somewhat slower than MD5. Besides, packages that aren't patched for blowfish won't work by default. 2) Controlling it with the tcb USE flag. This is possible, but seems silly. Although relevant, they are still two distinctly separate features. One can have blowfish support without tcb, and vice versa (at least I think so).
can you confirm the tcb thing, styx?
Yup, blowfish and tcb can be used independently.
how many ebuilds would use this flag?
Basically every package that uses crypt(3) can take advantage of this USE flag.
ok add it to use.desc, but please don't touch any stable packages with it, only ~arch masked ones.
Oki, thanks :)
