Edward Z. Yang wrote:
Ivan Lazar Miljenovic's wrote:
Edward Z. Yang writes:
I doubt you'd get very much runtime with that. I'd suggest prompting the
user to submit a failed build report if the build fails.
Exactly like how Windows keeps prompting you to allow it to send an
error report to
Heinrich Apfelmus apfel...@quantentunnel.de writes:
Perhaps exactly when the user is prompted?
Would you like to send an anonymous report of this build failure to
hackage.org? Users have been uploading 189 reports so far; yours would
be the 190th report that ensures high quality Haskell
Ivan Lazar Miljenovic wrote:
Heinrich Apfelmus writes:
Perhaps exactly when the user is prompted?
Would you like to send an anonymous report of this build failure to
hackage.org? Users have been uploading 189 reports so far; yours would
be the 190th report that ensures high quality Haskell
On Thu, Mar 11, 2010 at 08:54:15AM -0800, Rogan Creswick wrote:
(c) fix the unpacked version, and increment the version number by
adding a new level of detail (so, 3.1.0 becomes 3.1.0.1). This
version number never leaves my system -- it only exists to keep my
cabal/ghc-pkg consistent!
A
On Mon, Mar 8, 2010 at 2:31 PM, Maciej Piechotka uzytkown...@gmail.com wrote:
On Mon, 2010-03-08 at 15:37 +0100, Marc Weber wrote:
We can't expect package maintainers to test everything.
So it must be people like you and me who fixes those changes.
Well. Except that it require bumping
On Mon, 2010-03-08 at 15:37 +0100, Marc Weber wrote:
Hi Maciej,
that's why I started hack-nix.
You can patch dependencies easily.
However you have to install the Nix package manager.
It also works with lates versions only because the dependency solves is
written in Nix itself.
