Hello,
Here is the current patch countdown list. The next countdown will be on
October 8th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!947 Correct changes.tely entry and convert-ly rule for markup
> Would it be conceivable to do Homebrew builds also for (odd-numbered)
development versions of LilyPond?
According to homebrew rules, only stable versions are accepted. And really,
there is no * -devel package in the homebrew repository. About that, I
believe we can patch the formula until the
[Felix]
I was referring to the next minor version.
OK. If as you're proposing in the MR this gets
integrated in Homebrew via a fast path rather
than a release on our side, everyody's happy.
[Lukas]
[Jean]
What kind of next version, next minor of
current stable, i.e. 2.22.2, or next
stable
[Jean]
What kind of next version, next minor of
current stable, i.e. 2.22.2, or next
stable release, 2.24?
Which leads me to ask:
@Jefferson: Would it be conceivable to do Homebrew builds also for
(odd-numbered) development versions of LilyPond? LilyPond tends to have
a conservative policy
> What kind of next release, next minor to the current stable release ie
2.22.2, or next stable release 2.24?
I was referring to the next minor version.
> Regarding 2.24, hopefully we can have switched to Guile 2 permanently at
that point.
Sounds good, so homebrew users can hunt for bugs at
[Felix]
> I like the principle. However, Homebrew seems to want versioned tarballs, and I am not sure Phil and Jonas
should have to go through the multi-hour release process for this.
I believe it's okay for this change to wait for the next version
release of Lilypond.
What kind of next
> I like the principle. However, Homebrew seems to want versioned tarballs,
and I am not sure Phil and Jonas should have to go through the multi-hour
release process for this.
I believe it's okay for this change to wait for the next version release of
Lilypond.
Em ter., 5 de out. de 2021 às
On 2021-10-05 12:42 pm, Jefferson Felix wrote:
I just did this change locally, only the message is different (running
Guile 2), because someone also can build from source using guile 2.
I agree with this solution.
Would it make any sense for LilyPond in general to be able to report
Am Dienstag, dem 05.10.2021 um 16:44 -0300 schrieb Jefferson Felix:
> I have a question (I'm not very familiar w/ guile2 and lilypond source
> structure), but is it possible to build with guile1 and run with guile2,
> and vice-versa?
No, the lilypond executable links to either version of the
I have a question (I'm not very familiar w/ guile2 and lilypond source
structure), but is it possible to build with guile1 and run with guile2,
and vice-versa?
Em ter., 5 de out. de 2021 às 16:42, Jefferson Felix
escreveu:
> I just did this change locally, only the message is different (running
I just did this change locally, only the message is different (running
Guile 2), because someone also can build from source using guile 2.
I agree with this solution.
Em ter., 5 de out. de 2021 às 15:25, Jean Abou Samra
escreveu:
> [Lukas]
> > Would it be considered reasonable to hard-wire a
[Lukas]
Would it be considered reasonable to hard-wire a special
startup message in LilyPond proper if it is being built
with Guile2 (or rather: detects guile-2 on startup)?
I like the principle. However, Homebrew seems to want versioned
tarballs, and I am not sure Phil and Jonas should have
Folks,
Am 05.10.21 um 14:39 schrieb Jefferson Felix:
No problem, I was just pointing out the reasons why Guile 1.8.8 was
not approved by the homebrew core. I even believe this will help
advance Guile 2 compatibility, and certainly the Lilypond development
community will pick up on any bugs.
Yes, exactly. We don't use patches and code replacements are avoided as
much as possible.
Em ter., 5 de out. de 2021 às 09:53, Lukas-Fabian Moser
escreveu:
> Folks,
>
> Am 05.10.21 um 14:39 schrieb Jefferson Felix:
> > No problem, I was just pointing out the reasons why Guile 1.8.8 was
> > not
On 04.10.2021 19:42, Jean Abou Samra wrote:
This is just something I noticed, not of any direct importance to me,
but thought you might like to know. I checked convert-ly does not alter
the file.
This is registered as issue #4826,
https://gitlab.com/lilypond/lilypond/-/issues/4826
As an
We now have the formula on homebrew core.
I invite macOS users (mojave or higher) with Intel or M1 processors to test
it with:
brew install lilypond
Em sáb., 2 de out. de 2021 às 23:46, Jefferson Felix
escreveu:
> Ok, I understand, but strict homebrew core rules require me to submit a
> test
Am 05.10.21 um 01:41 schrieb Dan Eble:
I'd basically be interested in trying to understand the mechanics involved, but
seeing as term started today at our university, I'm sceptical I can spend
serious time on this before Christmas break. (And there's a fair chance it
would be above my head
Hello,
Here is the current patch countdown list. The next countdown will be on
October 6th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!939 Allow creating Scheme translators working in `\midi` - David
18 matches
Mail list logo
