> So I'm asking for comments: if you find these changes useful, and
> they work for you, perhaps they get included;
I don't build ghc much (but nhc98 has a darcs-all script too...), so
take my opinion with a pinch of salt. However, I do think both of these
changes are likely to be improvements: they remove otherwise-puzzling
behaviour.
> - if darcs-all or packages have changed, stop the script and
> ask the user to restart the darcs-all command, instead of
> continuing with outdated information
> - try summarizing any darcs warnings (file permission issues, ..),
> conflicts, and missing repos at the end of the run, so that
> they do not get lost if one keeps a verbose log
Suggestion: this is more likely to be acted on, if you file as a trac
bug report / enhancement request.
Regards,
Malcolm
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
