Bug 271637 - print/lilypond: update to 2.24.1
Summary: print/lilypond: update to 2.24.1
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Robert Clausecker
URL: http://lilypond.org/news.html#LilyPon...
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-25 18:44 UTC by Martin Neubauer
Modified: 2023-05-29 23:31 UTC (History)
1 user (show)

See Also:


Attachments
Patch updating to 2.24.1 (28.48 KB, patch)
2023-05-25 18:44 UTC, Martin Neubauer
m.ne: maintainer-approval+
Details | Diff
updated patch (29.62 KB, patch)
2023-05-25 23:36 UTC, Martin Neubauer
m.ne: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Neubauer 2023-05-25 18:44:39 UTC
Created attachment 242403 [details]
Patch updating to 2.24.1

- update to version 2.24.1
Comment 1 Robert Clausecker freebsd_committer freebsd_triage 2023-05-25 23:05:46 UTC
You have removed tex from USES but still have USE_TEX=latex in there.  Is this correct?

For the post-patch REINPLACE_CMD, check if you can replace the static REINPLACE_CMD uses with patch files as per policy.  REINPLACE_CMD should only be used for dynamic replacements, i.e. those where the substitution is dependent on a make variable or such.
Comment 2 Martin Neubauer 2023-05-25 23:36:21 UTC
Created attachment 242412 [details]
updated patch

- removed overlooked USE_TEX
- turned post-patch REINPLACE_CMD into regular patch
Comment 3 Martin Neubauer 2023-05-25 23:43:50 UTC
(In reply to Robert Clausecker from comment #1)
The USE_TEX line was an oversight; thanks for spotting this.

The REINPLACE_CMD, however, was already present when I adopted the port (I think...), and I just kept it there over the years. But as it is indeed a fully static change, and I'm not terribly attached to that line, it is now gone as well and replaced by a patch.
Comment 4 Robert Clausecker freebsd_committer freebsd_triage 2023-05-26 10:20:13 UTC
Thank you for the quick update.

I believe policy had changed a while ago regarding REINPLACE_CMD and instead of bulk-updating all ports, we're gradually changing ports over whenever there's an update.

Will commit your various submitted patches with my next batch.
There were some difficulties applying your previous patch, but I think I got it.
Comment 5 Martin Neubauer 2023-05-26 10:47:02 UTC
(In reply to Robert Clausecker from comment #4)
That does seem plausible, and I think that approach to implementing that new policy is quite sensible. On that note, I did that change to the patch for lilypond-devel as well.

Thanks for moving this forward.
Comment 6 commit-hook freebsd_committer freebsd_triage 2023-05-29 23:27:07 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=41234ceb6e1fa23aa50b5b680bf1e9d7333c8bcb

commit 41234ceb6e1fa23aa50b5b680bf1e9d7333c8bcb
Author:     Martin Neubauer <m.ne@gmx.net>
AuthorDate: 2023-05-26 10:16:31 +0000
Commit:     Robert Clausecker <fuz@FreeBSD.org>
CommitDate: 2023-05-29 23:24:05 +0000

    print/lilypond: update to 2.24.1

    Changelog: http://lilypond.org/news.html#LilyPond-2_002e24_002e1-released_0021-February-12_002c-2023

    PR:             271637

 print/lilypond/Makefile                            |  37 ++-
 print/lilypond/distinfo                            |   6 +-
 .../lilypond/files/patch-Documentation_GNUmakefile |  16 +-
 print/lilypond/files/patch-config.make.in          |   6 +-
 print/lilypond/files/patch-configure (gone)        |  77 -------
 .../patch-lily_include_includable-lexer.hh (new)   |  11 +
 .../lilypond/files/patch-lily_midi-item.cc (gone)  |  11 -
 ...info-vars.make => patch-make_texinfo-vars.make} |   8 +-
 print/lilypond/pkg-plist                           | 248 ++++++++++-----------
 9 files changed, 161 insertions(+), 259 deletions(-)
Comment 7 Robert Clausecker freebsd_committer freebsd_triage 2023-05-29 23:31:23 UTC
Thank you for your contribution.