Hi,
Mark H Weaver skribis:
> Ludovic Courtès wrote:
>> Mark H Weaver skribis:
>>
>>> Yes, of course, I agree that it's not possible to present a build plan
>>> ahead of time when grafts are enabled. That was the case before these
>>> changes, and it's the case today.
>>>
>>> The only part I
Hi Ludovic,
Ludovic Courtès wrote:
> Mark H Weaver skribis:
>
>> Yes, of course, I agree that it's not possible to present a build plan
>> ahead of time when grafts are enabled. That was the case before these
>> changes, and it's the case today.
>>
>> The only part I don't understand is why
Hi Mark,
Mark H Weaver skribis:
> Yes, of course, I agree that it's not possible to present a build plan
> ahead of time when grafts are enabled. That was the case before these
> changes, and it's the case today.
>
> The only part I don't understand is why you decided that "--dry-run"
> should
Hi Ludovic,
> Björn Höfling skribis:
>
>> On Mon, 13 Apr 2020 17:31:56 -0400
>> Mark H Weaver wrote:
>>
>>> I guess this is related to the recent changes in graft handling, where
>>> --dry-run (a.k.a. -n) no longer implies --no-grafts. It's not working
>>> well for me. I hadn't updated my
Hello!
Björn Höfling skribis:
> On Mon, 13 Apr 2020 17:31:56 -0400
> Mark H Weaver wrote:
>
>> I guess this is related to the recent changes in graft handling, where
>> --dry-run (a.k.a. -n) no longer implies --no-grafts. It's not working
>> well for me. I hadn't updated my system since
On Mon, 13 Apr 2020 17:31:56 -0400
Mark H Weaver wrote:
> I guess this is related to the recent changes in graft handling, where
> --dry-run (a.k.a. -n) no longer implies --no-grafts. It's not working
> well for me. I hadn't updated my system since before those grafting
> changes were made,
I guess this is related to the recent changes in graft handling, where
--dry-run (a.k.a. -n) no longer implies --no-grafts. It's not working
well for me. I hadn't updated my system since before those grafting
changes were made, and there's a lot for me to rebuild (I don't use
substitutes). I
