-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any comment about upcoming Git Rev News edition 118 #741
Comments
Two Outreachy interns have been selected and should start working on their internship on December 9th. They have sent emails to the mailing list: |
@jnareb maybe we could add a link to this LWN article about adding Rust to Git? |
Yes, I agree that would be a good idea (perhaps with reference to Edition 82?). |
@jnareb maybe we could add a link to this short one about upcoming Git 2.48 too? |
That's a good idea. Thanks @chriscool for the suggestion. By the way, do you have any reference to discussion about choosing "Meson to be the primary build tool for Git in the future"? |
@jnareb I think most of the discussion about Meson happened in that thread: https://lore.kernel.org/git/[email protected]/ Do you mean that I should cover this in an article? |
Thanks, though that thread looks like quite far in the process, being v8 of "Modernize the build system" series... I have just now remembered that the idea of Git switching to a modern build system was discussed on Git Contributor's Summit 2024: https://lore.kernel.org/git/[email protected]/
I think I was one of people proposing autoconf as an addition to configuring Git via Makefile variables very early in the life of Git as a project - it made it much easier to create RPM spec file when compilation follows traditional 'configure && make && make install' steps. But the Linux ecosystem have much changed since then. For example Meson is 8 years younger (2013) than Git (2005). CMake is older than Git (2000), but not much. I guess Build2 is too new for the consideration...
If you don't have a better idea for a topic, and have time for some research - it would be IMVHO interesting topic. |
I see that the following promise from Git Contributor's Summit 2024 (https://lore.kernel.org/git/[email protected]/)
There is now Documentation/technical/build-systems.txt, written by Patrick Steinhardt (@pks-t). |
Actually I already started writing the blob post that GitLab will publish about the upcoming v2.48.0 and we might talk about the Meson build system if it is part of that release (otherwise it will hopefully be part of the next one). So I have started researching the subject a bit, and yeah around 2006 it looks like you introduced and worked on the configure.ac file to add autoconf build support to Git. I will see if I have time to work on an article for Git Rev News about it... |
@chriscool , whether the information about modernizing the build system, choosing Meson, and adding support for it will be on GitLab Blog (perhaps in the future), or as an article in Git Rev News - in my opinion it does not matter, it is important that the information is or will be there. |
A currently mostly empty draft is there:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-118.md
Feel free to comment in this issue, suggest topics, suggest persons to interview, or use the edit button (that looks like a pen) to edit and create a pull request with the changes you would like.
Let's try to publish this edition around the end of December 2024!
Thanks!
cc @jnareb @mjaix @sivaraam @gitster @stepnem
The text was updated successfully, but these errors were encountered: