Bug 239614 - x11-toolkits/libgdiplus: Update to 6.0.1
Summary: x11-toolkits/libgdiplus: Update to 6.0.1
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-03 13:33 UTC by Phillip R. Jaenke
Modified: 2020-06-21 23:27 UTC (History)
5 users (show)

See Also:
salvadore: maintainer-feedback-


Attachments
x11-toolkits_libgdiplus.shar (2.63 KB, text/plain)
2019-08-03 13:33 UTC, Phillip R. Jaenke
no flags Details
Update to 6.0.4, take maintainership (16.13 KB, patch)
2020-03-17 18:51 UTC, Phillip R. Jaenke
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Phillip R. Jaenke 2019-08-03 13:33:48 UTC
Created attachment 206237 [details]
x11-toolkits_libgdiplus.shar

libgdiplus 6.0 was branched and released on Friday. This update now uses x11-toolkits/pango for significantly improved text rendering, especially for i18n.

This also corrects an invalid license assignment. libgdiplus is MIT licensed. It has never been GPLv3 licensed.
Comment 1 Phillip R. Jaenke 2019-08-25 12:56:05 UTC
No maintainer feedback or response in 21 days.
The mono@ mailing list has had absolutely no non-automated traffic for over a month.
Comment 2 Phillip R. Jaenke 2019-09-15 03:24:24 UTC
Can we please get this in? I haven't had time to make a cleaner diff due to other issues, and this really needs to get in before Q4.
Comment 3 Phillip R. Jaenke 2020-03-17 18:51:00 UTC
Created attachment 212466 [details]
Update to 6.0.4, take maintainership

There has been no movement or response on this port for over a year, and multiple releases have been put out - including one which addresses the need for port-specific patches. 

Attached diff updates to 6.0.4 and takes maintainership. Since this is part of the Mono project, I'm already familiar with it and in regular touch with the developers.
Comment 4 Lorenzo Salvadore freebsd_committer 2020-04-14 15:18:08 UTC
Take the bug as mono@ seems to be inactive.

I will test your changes and then commit them.
Comment 5 Lorenzo Salvadore freebsd_committer 2020-04-14 15:23:24 UTC
Gerald, Tobias (my mentors): How should I proceed with maintainership? I have been told that the mono@ team is completely inactive (or even inexistent). I don't doubt that it is true and indeed this PR prooves it, but do we have some official way to check it? And once I checked it, could I reset port maintainer for all mono@ ports?
Comment 6 Tobias C. Berner freebsd_committer 2020-04-14 15:51:07 UTC
Moin moin 

In my opinion I would prefer prj becoming part of mono@ (or from what it seems the whole mono@ ;) ) instead of becoming the "sole" maintainer. 

That being said, if what it takes for this port to be maintained, full steam ahead :)


mfg Tobias
Comment 7 Lorenzo Salvadore freebsd_committer 2020-04-15 13:24:29 UTC
Philippe, last patch you submitted puts the license back to GPLv3: I guess that was a mistake, wasn't it?

Indeed, I agree that the software is MIT licensed and I would then commit your patch adding the following changes:
-LICENSE=       GPLv3
-LICENSE_FILE=  ${WRKSRC}/COPYING
+LICENSE=       MIT
+LICENSE_FILE=  ${WRKSRC}/LICENSE

(The COPYING file is a small file telling reader to read LICENSE: let's put directly LICENSE in LICENSE_FILE then.)

Testing went fine and as soon as you confirm that the license should be changed to MIT or explain why it should stay GPLv3 I will commit your patch.