Summary: | tcl-8.3.3.ebuild and tk-8.3.3.ebuild shouldn't cause tcl and tk to be threaded | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | kevin |
Component: | [OLD] Development | Assignee: | Stanislav Brabec <utx> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | agriffis, mholzer, mkennedy, perl, port001, seemant |
Priority: | High | ||
Version: | 1.1a | ||
Hardware: | x86 | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=868468 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 17181 | ||
Attachments: | tcl ebuild with threads USE flag |
Description
kevin
2002-04-23 02:11:04 UTC
sounds like we should disable threads with tcl/tk Disabled in tcl-8.3.3; will be a use flag later on when we have a consistent policy for handling ebuild-specific use flags. Disabling threads blocks the aolserver (bug #17181) from being submited to portage because it requires tcl to be built with --enable-threads. Perhaps we could use an internal USE flag for the time being? Created attachment 19633 [details] tcl ebuild with threads USE flag I've attached the modified tcl ebuild I'm using which has a 'threads' USE flag just in case its useful to anyone else. It makes merging <a href="http://bugs.gentoo.org/show_bug.cgi?id=17181">aolserver</a> easier. Sorry. I don't have capacity to deal with the tcl and tk stuff anymore. Stanislav, thoughts? Stanislav, if you don't have any objections I'm going to go with the local USE flag. This bug is holding up 4 others. so we could make "threads" as global flag it's also used in dev-lang/perl:threads - Enable Perl threads, has some compatibility problems dev-lisp/clisp and dev-lisp/sbcl are two more ebuilds which can use a threads flag I'd vote for a global threads flag. With the upcoming portage it could even be set per-package. seemant: what do you think about a global threads USE-flag ? marty, I don't know -- I think perl uses that -- but it's sort of a hidden flag because it could lead to dangerous things -- maybe sommething similar here? perl team, please tell us about the threads flag a little more Threads in perl will cause a number of compatibility problems as most people know. This is even more problematic in terms of things like mod_perl-like environments, from what I've heard. Very few perl apps or modules make use of threads due to their buggy nature and I think most people are willing to hold out for perl6 for a decent thread implementation. As long as it's not on by default, a threads USE flag is fine, but I wouldn't be surprised if we see a slight upswing in perl bugs because of it. I believe that the perl ebuild currently uses a env variable to handle enabling and disabling of threads - maybe this could be used for tcl as well? My concern is that someone will enable a threads use flag for tcl and all of sudden have wacky problems with perl. If nobody has any objections, I'm going to goahead with this. I think i'll accompany a paused warning too. Anyone mind if I get rid of a few old ebuilds while I'm at it? in CVS. |