Implementation-Agnostic Support for Alternative Compilers: ccache, distcc, etc.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devscripts (Debian) |
Fix Released
|
Unknown
|
|||
devscripts (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: devscripts
I have been using debuild for quite a while now, mainly because I know
that one of its goals is to sanitize the build environment. In any
case, I have interest in having it support a ccache or distcc
environment as elegantly as possible. What I have done here is provide
an additional CLI option that allows the user to prepend another
search location to the sanitized ${PATH}. Why I have chosen this route
is that it allows the packager to bypass a standard suite of compilers
in ${PATH} in favor of aliases, bootstrappers, job distributers, or
whatever else anyone can imagine. It's pretty implementation-
I see this approach to being somewhat cleaner than providing explicit
support for ccache or distcc in debuild, as not doing this would
require debuild henceforth to follow ccache or distcc's environment
variable configuration rules. I'm sure none of you want to track the
specifics of their implementation. Plus, this is better than
explicitly overriding the ${PATH}, as one can do now to achieve this,
because this does not require the end-user to constantly track
debuild's implementation nor ${PATH} rules as the Linux FHS changes
over time.
What are your thoughts?
I've attached a patch that I made. And---yes---the patch includes
modifications to the manual pages. ;-) I also submitted an updated package to REVU, but I'm not confident that my GPG is properly registered.
Changed in devscripts: | |
status: | Unknown → New |
Changed in devscripts: | |
status: | New → Fix Committed |
Changed in devscripts: | |
status: | Fix Committed → Fix Released |
Resubmission due to browser crashing during POST. :-/