[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Sat, 23 Jul 2016 16:52:20 +0200
On Sat, Jul 23, 2016 at 01:03:07PM +0200, Ludovic Courtès wrote:
> For the current solution (avoiding a full rebuild), see commit
> 61dc82d9b90d0545739c30bfc33003bd062071f0. LilyPond could hard-code the
> file name of ‘gsc’.
This looks like too much work to implement for each package separately.
And as a permanent solution, I do not like it.
> Alternately, we could provide a wrapper containing a ‘gs’ symlink.
This would be one option. Or we could add another package, corresponding
to the previous definition, that we would use only as an input to the
packages in core-updates that do not build right now. This solution could
be implemented using copy-paste and not take much time. I would then also
remove the ad-hoc lilypond patching.
Then after core-updates is merged, we could add the gs->gsc link to our
What do you think?
- Gs, Andreas Enge, 2016/07/22
- Re: Gs, Ricardo Wurmus, 2016/07/22
- Re: Gs, Ludovic Courtès, 2016/07/23
- Re: Gs,
Andreas Enge <=
- Re: Gs, Ludovic Courtès, 2016/07/25
- Re: Gs, Efraim Flashner, 2016/07/24
- Gs, Federico Beffa, 2016/07/23