I would be very cautious about automating bug reports
for gcc. The last thing we need is upstream getting irked
over a flood of bootstrap failures that are due to incorrect
local configurations. Darwin is already treated as a free
loader by upstream (hence the target depreciation). Abusing
the
I suggest that fink be enhanced to do what some other systems have
been doing lately: package up all the info for a bug report and send
it to the right place (after the user has a chance to look it over
and say OK).
The above functionality would replace the stdout dump of
do-it-yourself
Dave Yost wrote:
I suggest that fink be enhanced to do what some other systems have been
doing lately: package up all the info for a bug report and send it to
the right place (after the user has a chance to look it over and say OK).
The above functionality would replace the stdout dump of
