Closed Bug 1100174 Opened 10 years ago Closed 10 years ago

Make AUTOCLOBBER=1 the default

Categories

(Firefox Build System :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: n.nethercote, Unassigned)

References

Details

AUTOCLOBBER=1 should be the default. Reasons:

- It's annoying to start a build, switch to doing something else, then check back on progress a while later and find that it's been idle because a clobber was needed.

- It seems like only experts would want to not auto-clobber, and they are exactly the people who should be able to specify extra stuff in their mozconfig without difficulty. It's just one more thing for newbies to get wrong.

Any counter-arguments?
There was discussion in bug 863091. IIRC there was also a mailing list thread or 2 that sparked changing it.

Nobody is happy with the default either way. I think the best outcome is to eliminate clobbers entirely. We all know how well that is going...
(In reply to Nicholas Nethercote [:njn] from comment #0)
> Any counter-arguments?

Autoclobber destructively destroys whatever data you had in the build directory. If you're keeping some data in the build directory and you go clobber that away, you have pure dataloss. In particular, this might hit people who compile multiple open-source projects harder--I tend to routinely pipe some extra compilation debugging information into text files, and unexpectedly losing those would be rather frustrating.

I will note that Thunderbird doesn't actually support CLOBBER (if you change the m-c CLOBBER file, TB will happily build without clobbering), and in the past year or so, I can think of only two or three times that it actually needed to be clobbered to build--which suggests that most of the CLOBBER changes affect comparatively less common build platforms (*cough*Android*cough*).
(In reply to Joshua Cranmer [:jcranmer] from comment #2)

+1
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
The last comment in bug 863091 is one year ago. Why can it be a duplicate?
We've already had a lengthy discussion about whether to auto clobber by default or not. Nothing has changed since we last had the conversation. The previous decision stands.
Bug 863091 is making AUTOCLOBBER=1 opt-in and this bug suggested making it opt-out. I'm fine with the decision, but this bug can't be a dupe.
Resolution: DUPLICATE → WONTFIX
See Also: → 863091
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.