Issues 2008-10-15
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
|
 
Still loading...
ABCDEFG
1
IDVotesType/MemberMilestonePriOwnerSummary/Comments
2
3
22201DEFECTtriageP4issues@sconsVariantDir Enhancement
4
consensus
5
6
Bill
7
Brandon
8
David
9
Garyp4who?ok to close and make a new issue, but I think it's going to come down to Steven anyway... seems like it's deep in the core code. But I'd like a better testcase (one that doesn't call builders from other builders -- danger!)
10
Greg1.x?p4who?I'm divided about what to do with this issue, since the original issue was on a topic that's not the current focus. It would make sense to close this issue as INVALID and create another issue (with a different subject!) to be the focus of the fix. That said, it looks like it worked at some point, so there was some change that caused it. I'd like to know what that change fixed. I'd like to see this issue tackled in the 1.x timeframe, but I could understand if it slid to later.
11
Jim
12
Ken
13
Sohail
14
Stevenresearchp4not me?I'll take it if we can't find someone else, but it would probably benefit from someone with a fresher approach and less mental baggage around the issue than me. I'm suggesting "research" because I'm not clear about Greg's suggestion that something used to work? Jon M's comment suggests that it failed under all SCons versions he tried. I agree about marking this INVALID and opening up a new issue to clarify exactly what we're trying to fix.
15
16
22250DEFECTtriageP4issues@sconsWrong escaping of paths containing parentheses
17
consensus
18
19
Bill
20
Brandon
21
David
22
Gary1.xJimJim, I'm pretty knowledgeable about quoting too, so if you want to bounce ideas off someone, I'm your man.
23
Greg1.x?Jim?Is Jim still around? Also note that the move to subprocess will cause a crisis in quoting, since we will be able to use its quoting facility, which will require all of our ad-hoc quoting to be reexamined to make sure it doesn't conflict.
24
JimJimJim is around, but has been crazy busy - my apologies. Agreed with quoting problems - I've started applying some bandaids, but I think some thinking is needed about the problem in general, not bandaids. I'll see if I can come up with at least a start of discussion over the next few days. In principle, would be great if we could remove a lot of the ad-hoc quoting, and subst_list to boot, as that's a quoting disaster on wheels
25
Ken
26
Sohail
27
Steven1.xJim, if possibleProbably me, if not. Agreed re: crisis in quoting, but it's something that's been needed for quite some time. We should find out if Jim's available for any of this or if we should move on.
28
29
22260PATCHtriageP4issues@sconsCheckFuncsOnce: to speed up functions check
30
consensus
31
32
Bill
33
Brandon
34
David
35
GaryWONTFIXwhat Steven said.
36
Greg2.x+toolchainPatch isn't compatible with 1.5.2, the name is terrible, and it doesn't integrate with what little caching there is, but it's not a bad idea. I think this should be added to the stack of ideas for the toolchain rework.
37
Jim
38
Ken
39
Sohail
40
StevenWONTFIXIs this really a good idea? If you check for multiple things at once and it fails the compilation because only some of them are available, well, you don't really have sufficient information to know what to do. It seems to me that the point of the fine-grained Autoconf checks is that it's easier to compose them into more complicated logic than decompose coarse-grained tests. I'll go with this if Autoconf has some similar functionality, but without that, it seems like a pretty negligible corner case that's better handled anyway by checking for the individual functions.
41
42
22270ENHANCEMENTtriageP4issues@sconsIdea to support msys scripts from ParseConfig
43
consensus
44
45
Bill
46
Brandon
47
David
48
Gary2.xp3ParseConfig would be useful under msys no doubt, but it's a minefield (see ML discussions); quoting, filename syntax, etc. This patch *might* be a step towards sorting it out though. The basic idea seems good. Maybe have the OP work up something and post to the wiki, asking for comments.
49
Gregno ideanot me!Looks complicated and requires manual setup by the user, but I'll defer to the consensus.
50
Jim
51
Ken
52
Sohail
53
Steven2.x?not sureShould find an MSYS guru who can do a thorough job with supporting it. It seems like this is the sort of thing that's really easy to include out of ignorance of the larger implications, only to find later that we've boxed ourselves in to supporting backwards compatibility for a broken model...
54
55
22280ENHANCEMENTtriageP4issues@sconsBackward compat for os.devnull
56
consensus
57
58
Bill
59
Brandon
60
David
61
Gary1.2p2Stevenconsensus.
62
Greg1.2p2StevenWould simplify use of subprocess.
63
Jim
64
Ken
65
Sohail
66
Steven1.2p2SKEasy to do, helps makes things better, no reason to put it off.
67
68
22290FEATUREtriageP4issues@sconsExport() should allow keywords to identify exported values
69
consensus
70
71
Bill
72
Brandon
73
David
74
Gary2.xp2gregwhy not.
75
Greg2.xp2???It doesn't seem complicated, so I'm willing to take a swing at it in the 2.x timeframe.
76
Jim
77
Ken
78
Sohail
79
Steven2.xp2gregnoelGood idea.
80
81
22300FEATUREtriageP4issues@sconsAdd Cons-style validation of target file contents
82
consensus
83
84
Bill
85
Brandon
86
David
87
Garywheneverp3StevenWould be a good idea. It's bitten me before too, and recent ML discussions show several valid use cases.
88
Greg???It's bothered me that SCons doesn't do this, so I think it should be done. Steven, how hard is it? I know nothing about that part of SCons, so I can't judge.
89
Jim
90
Ken
91
Sohail
92
Steven1.xp3SKShouldn't be all that hard. I'm the logical person.
93
94
22310DEFECTtriageP4issues@sconsAdd --warn=all-deprecated command-line option
95
consensus
96
97
Bill
98
Brandon
99
David
100
Garydon't knowwhatever you guys decide
Loading...
 
 
 
Sheet 1