On Mon, Dec 3, 2012 at 1:48 PM, Malcolm Wallace wrote:
>
> If the scheme is going to work at all, it must update _every_ version of
> text-foo that could be affected.
>
> Is that an unrealistic expectation?
It at least demands the process be automatable, but then perhaps
that's already a good id
Malcolm Wallace writes:
> On 3 Dec 2012, at 11:35, Herbert Valerio Riedel wrote:
>> 2) there's a package text-foo which depends on 'text >= 0.10' (i.e. with no
>> upper bound), for which N versions exist on Hackage (all with
>> the same 'text >= 0.10' constraint):
>>
>> 0.1.0, 0.1.0.1, 0.
Mon Dec 3 09:23:07 GMT 2012 Edsko de Vries
* Use pure restore for build reports
Ignore-this: 20c2365b3052a865266be10a57654e27
This is the last feature to be converted. Next up: remove all the scaffolding
and the now obsolete impure restore types.
M ./Distribution/Server/Features/
On 3 Dec 2012, at 11:35, Herbert Valerio Riedel wrote:
>
> 2) there's a package text-foo which depends on 'text >= 0.10' (i.e. with no
> upper bound), for which N versions exist on Hackage (all with
> the same 'text >= 0.10' constraint):
>
> 0.1.0, 0.1.0.1, 0.1.0.2, 0.1.1, 0.1.2, 0.2, ...
Duncan Coutts writes:
[...]
> I mentioned I'd written a feature to update the .cabal file we use
> when building with the same one as is in the package archive index.
> I've now pushed that to the head branch. I think it would be good to
> have on the 1.16 branch and included in the cabal-instal
