[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Address output-distance problems: (issue 563730043 by address@hidden
From: |
David Kastrup |
Subject: |
Re: Address output-distance problems: (issue 563730043 by address@hidden) |
Date: |
Thu, 12 Mar 2020 18:11:56 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Kevin Barry <address@hidden> writes:
>>
>>
>> Frankly, I am more sympathetic to "worksforme" discussions among
>> developers than telling users "worksforme". Where is the point in being
>> able to tell users that no developer will reproduce their problem?
>>
>> I'd rather have an error popping up for at least some developers than
>> for none.
>>
>
> This sounds like you are saying it's better for the situation to be a mess
> for developers so that they can better help users deal with the same mess,
> therefore we should leave things as they are.
I say that having a developer monoculture doesn't buy as anything since
we still need to provide for a multitude of users.
> Installing docker and building an image is much easier than setting up
> a working build environment for LilyPond now.
Get a LilyPond source .deb and do sudo apt build-deps on it. Afterwards
you have a working build environment.
> I think it would be a win for both devs and users.
I don't really see the underlying logic. Users should consider it a win
when the developers state "you are no longer allowed to run LilyPond
natively, get a docker container", and you want to convince developers
to stop using and developing LilyPond natively on their systems because
it will be so much easier to maintain a virtual layer in between?
We have had the LilyDev VM for a long time now. It has seen some use,
but not overwhelmingly much, and the reasons for that are pretty much
the same for newer virtualisation methods.
--
David Kastrup
- Re: Address output-distance problems: (issue 563730043 by address@hidden), (continued)
- Re: Address output-distance problems: (issue 563730043 by address@hidden), dak, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), pkx166h, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), Han-Wen Nienhuys, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), David Kastrup, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), pkx166h, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), Kevin Barry, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), pkx166h, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), Kevin Barry, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), David Kastrup, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), Kevin Barry, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden),
David Kastrup <=
- Re: Address output-distance problems: (issue 563730043 by address@hidden), Kevin Barry, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), Han-Wen Nienhuys, 2020/03/13
- Re: Address output-distance problems: (issue 563730043 by address@hidden), Dan Eble, 2020/03/12
- Re: Address output-distance problems: (issue 563730043 by address@hidden), Kevin Barry, 2020/03/13
- Re: Address output-distance problems: (issue 563730043 by address@hidden), David Kastrup, 2020/03/13
- Re: Address output-distance problems: (issue 563730043 by address@hidden), Dan Eble, 2020/03/13
- Re: Address output-distance problems: (issue 563730043 by address@hidden), Jonas Hahnfeld, 2020/03/12
Re: Address output-distance problems: (issue 563730043 by address@hidden), jonas . hahnfeld, 2020/03/12
Re: Address output-distance problems: (issue 563730043 by address@hidden), jonas . hahnfeld, 2020/03/12
Re: Address output-distance problems: (issue 563730043 by address@hidden), dak, 2020/03/12