rubber always returns true
Bug #412465 reported by
Michael Schnupp
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Rubber |
Confirmed
|
Low
|
Unassigned | ||
rubber (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: rubber
rubber should return a different exit value, depending on whether it had to modify the output file.
After printing a "nothing to be done for $target" it should return false, allowing for example shell scripts or make files to easily decide if further action is required.
Changed in rubber: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Paul Kishimoto (khaeru) |
milestone: | none → 1.2 |
Changed in rubber (Ubuntu): | |
status: | New → Confirmed |
Changed in rubber: | |
assignee: | Paul Kishimoto (khaeru) → nobody |
Changed in rubber: | |
milestone: | 1.3 → 1.4 |
Changed in rubber: | |
milestone: | 1.4 → none |
milestone: | none → 1.5 |
Changed in rubber: | |
milestone: | 1.5 → none |
To post a comment you must log in.
Hi,
Currently, rubber returns false if some processing failed, and true if everything went fine. This is standard behaviour: not doing anything because the output document is up to date is not a failure. I do think it is the way it should be.
I admit that it might be useful in some situations to detect if some processing was actually performed. However, I don't know of a standard way for a command to return such information. It would be easy to add a command-line switch so that false is returned when nothing was done, but then how could one distinguish that from an actual failure?
Emmanuel