View Bug #263
Summary: Replacing a component with a directory can mess up object file cache
| Difficulty:
2 |
|
Version goal:
Future |
|
| Status:
Unassigned |
|
Reported by:
Marcus Ramberg |
|
| Version found:
Ongoing |
|
Severity:
Minor |
|
| |
Description
Replacing a component with a directory, or vica versa, may cause a situation where Mason is unable to create the associated object files. Mason must thoroughly search for and unlink (or more likely, rename) old object files/directories when a mkpath fails.
History
| Jun 14, 2001 04:28 PM |
|
Jonathan Swartz created bug.
|
| Jun 14, 2001 04:28 PM |
|
Jonathan Swartz set version_found to Ongoing.
|
| Jun 14, 2001 04:28 PM |
|
Jonathan Swartz set difficulty to 2.
|
| Jun 14, 2001 04:28 PM |
|
Jonathan Swartz set version_goal to 1.1x.
|
| Jul 20, 2002 06:01 PM |
|
Dave Rolsky
writes: This seems pretty low priority since naming a component and a directory _exactly_ the same thing is just dumb.
|
| Oct 10, 2002 03:51 PM |
|
Jonathan Swartz changed version_goal from 1.1x to 2.0.
|
| Oct 10, 2002 03:51 PM |
|
Jonathan Swartz
writes: While I don't necessarily agree with Dave's wording, I agree that the difficulty of this outweighs the priority. Putting into the "eventually" bucket.
|