Heya,

while I was emerging dev-libs/sqlite, I noticed that it uses USE=threadsafe to distinguish between threadsafe and non-threadsafe builds. While this is not strange per-se, lots of (?) other packages seem to make that decision based on USE=threads (dev-lang/php, dev-db/postgresql-base, ...). I think we should be consistent here, i.e. either change the two packages, which are using USE=threadsafe (dev-libs/sqlite and dev-lang/spidermonkey), to use "threads" instead or the other way round. I guess the easiest way would be to move from "threadsafe" to "threads", but I'm not sure whether this is really the better alternative. "threadsafe" sounds more appropriate to me in those cases, but there would probably be a huge amount of work required to change that. Now the question is: What do you think is the better way of making this consistent? :)

--
Christian Hoffmann

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to