build-support/release changes

[mornfall]

No description provided.

[peti]

I find it hard to judge whether to merge this patch or not because there is no description of what it does. I'm no VM expert, though, so maybe others don't have that problem.

Also, it's not clear to me how the change to haskell-defaults.nix fits in with the rest of the patches.

[mornfall]

1. haskell-defaults are not part of this request
2. the commits have comments and should be reasonably obvious

(Hmh. Apparently, github changes existing pull requests after the fact. That wasn't at all clear. So I am supposed to freeze a branch while a pull request is active? That seems quite silly...)

[shlevy]

@mornfall You can change the commit range for a pull request, I think.

[peti]

mornfall, how do you plan to proceed with this request? As it is now, it contains seemingly unrelated patches to Haskell packages.

[peti]

I committed some of your patches manually (i.e. the RPM update and the refactoring). Could you please merge the current master branch into your forked copy (or even better; rebase your forked copy relative to the current master from the upstream repository) and push the result to update this pull request, please?

[mornfall]

Rebased. I use this branch to feed a Hydra instance somewhere, and I don't feel like maintaining multiple branches. Please cherry-pick at will, I'll rebase this from time to time. Maybe the pull request should be closed though? I have no idea what the best procedure is. Apparently, pull requests update themselves when I push to my branch, which is something that probably makes them awkward for this use.

[peti]

Mornfall, I'm not sure what to do about this request. I have committed some of your changes, and they ended up breaking other builds. On that occasion, I would have expected you to step up and make an effort to fix those errors, but nothing happened, so the commits had to be revoked. Given these circumstances, I don't want to commit any further patches unless I can personally maintain them. That is not the case for the patches in this pull request, so I will not commit them. Maybe someone else will, but so far it doesn't look like it.

[shlevy]

@mornfall I'm closing this PR. If you have specific changes you want merged in, please put them in a separate branch explicitly for merging.

[mornfall]

Well, if someone told me that these patches broke something, I'd have tried to fix that at least. But with the amount of paperwork that goes with anything around here... I guess I'll just maintain a fork. You know, github won't tell me that something got merged, and I don't have time to monitor each patch going into nixpkgs to check if it wasn't something from my branch and if it was whether it broke anything. If you have a list of things that are likely to break when I work on build-support/vm, give me a list and I can add those things to my own hydra (http://anna2.fi.muni.cz:3000 these days). I'll try to keep everything in working order.