[RUBY] A story about sending a pull request to MinGW to update the libgr version

Introduction

Hello. I have updated the MinGW package, so I will write it as an article.

Why do I have to update the MinGW package?

I think everyone uses package managers, but I think that surprisingly few people have been involved in the maintenance. This is the first time for me to update the MinGW package.

About a year ago, I have been making graph drawing software GR.rb for Ruby for both hobbies and profits. image.png

GR.rb is a binding for libgr. I don't usually use Windows. However, thankfully there was a request to support Windows, so I asked Detailed person to do everything from creating PKGBUILD to registering the libgr package with MinGW. It was.

After that, a little time passed, and the version of the original libgr will be upgraded little by little, so I thought that it was time to update, so I lifted my weight and updated from 0.50.0 to 0.51.2.

Updating the MingGW package wasn't difficult as a result, but I felt very lonely because there was no Japanese experience article that updated the MinGW package. Write a Qiita article to help someone.

manner

The basic method is the same as homebrew.

MSYS2 official page https://www.msys2.org/wiki/Creating-Packages/

It contains the information you need, so it's a good idea to take a quick look at it using Google Translate.

git clone

git clone https://github.com/Alexpux/MINGW-packages
cd MINGW-packages/mingw-w64-gr

You can change ʻorigin` later, but it's easier to work if you fork from the beginning.

git clone https://github.com/YOURNAME/MINGW-packages
cd MINGW-packages/mingw-w64-gr

Editing PKGBUILD

Update the package version number.

PKGBUILD


pkgver=0.51.2

update sha256sum

PKGBUILD


sha256sums=("E6A3D0ED911F6E59CC2293B5694EE18A0620849E666143870A9EDA71C02BB833")

Also, this time, the patch that was applied last time seemed unnecessary, so I removed it.

Build and install

makepkg-mingw -sCLf
pacman -U mingw-w64-*-gr-*-any.pkg.tar.xz

You can do it with.

Send a pull request

If that's okay, cut the branch and send a pull request. Don't forget

git pull --rebase

The name of the branch looks good, but I chose gr-0.51.2. The commit of the pull request is mixed with uppercase and lowercase letters, but it seems that you can do gr: Update to 0.51.2 or gr: update to 0.51.2.

After submitting the pull request, make sure that the CI has passed. If it has passed, the person who is maintaining it should check it and merge it.

This PR was successfully merged within a few hours. It seems that maintenance is being carried out quite actively.

in conclusion

MinGW is not scary if you just update the version!

That's all for this article.

Recommended Posts

A story about sending a pull request to MinGW to update the libgr version
Send a pull request to GitHub
A story about making a calculator to calculate the shell mound rate
A story about the JDK in the Java 11 era
A story about making a Builder that inherits the Builder
A story about trying to operate JAVA File
[Ruby] Sending a POST HTTP request to the Web API using OAuth authentication
A story about trying to get along with Mockito
A story about trying hard to decompile JAR files
A story about reducing memory consumption to 1/100 with find_in_batches
Update to the latest version without specifying the version with gradle wrapper
[Rails] A story that continued to incorrectly verify the reason why the update action did not pass (update)
A story about using the CoreImage framework to erase stains with Swift and implement a blur erase function
A note about the scope
A story about hitting the League Of Legends API with JAVA
AWS Cloud9 environment construction Update Ruby to the latest stable version
A story about changing skills from COBOL cultivated for 5 years in the late 20s to a Web language