git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC] My Git Dev Blog

From
Bagas Sanjaya <bagasdotme@gmail.com>
Date
May 23, 2021, 08:10 UTC
Message-ID
<f1fca31b-17b8-9dbb-4d46-dda8c44645c1@gmail.com>
In-Reply-To
<35493133-2504-4CAE-B700-79EAB990DD17@gmail.com>
Hi Atharva,
On 22/05/21 23.42, Atharva Raykar wrote:
Show 14 quoted lines
> Hi all,
> 
> As is tradition, I have started my weekly GSoC blog :)
> 
> Here is week 1: https://atharvaraykar.me/gitnotes/week1
> 
> I shall be sharing my progress, thoughts, experiences and any
> information that might help future contributors in my blog.
> 
> After my GSoC period, I hope to convert it into a blog that
> will help pull in and guide new contributors to Git development.
> 
> Any kind of feedback will be appreciated!
> 

You said on your blog that you switched your development environment from Linux (what the distro you used previously?) to macOS. Why did you make the switch?

Next, you mentioned that you set up emacs config for Git developers (ones that contribute code to git.git). Since I use (r)vim instead of emacs as my editor, what are similar configs for vim?

And finally, you said that you had to deal with "header not found" errors. I asked these questions:

   1. You mentioned that in order to link against gettext on non-standard
      path, you did:
> ./configure "LDFLAGS=$LDFLAGS -L/opt/homebrew/Cellar/gettext/0.21/lib" \
>      "CFLAGS=-I/opt/homebrew/Cellar/gettext/0.21/include"
      Why did you use full path to gettext? I suspect that you can instead
      use `LDFLAGS= $LDFLAGS -L/opt/homebrew/lib \
      CFLAGS=-I/opt/homebrew/include`, because when you install a library
      using homebrew, it will symlink the library location from homebrew
      standard hierarchy (/opt/homebrew/{lib,include}) to actual location
      (/opt/homebrew/<User>/<package>/<version>/{lib,include}).
   2. Can these procedure above for linking Git against libraries at
      non-standard locations (such as /opt) be applicable also to Linux
      systems? Try to adapt that procedure on your Linux system (if
      available), with custom-compiled newer version of any of Git
      dependencies (such as gettext).
Thanks.
-- 
An old man doll... just what I always wanted! - Clara
Previous: Atharva RaykarNext: Atharva Raykar
Message 4 of 13 in “[GSoC] My Git Dev Blog”
  1. Atharva RaykarMay 22, 2021
  2. Philippe BlainMay 22, 2021
  3. Atharva RaykarMay 23, 2021
  4. Bagas SanjayaMay 23, 2021
  5. Atharva RaykarMay 23, 2021
  6. Felipe ContrerasMay 30, 2021
  7. Christian CouderMay 24, 2021
  8. Atharva RaykarMay 30, 2021
  9. Kaartic SivaraamMay 30, 2021
  10. Atharva RaykarMay 31, 2021
  11. Bagas SanjayaMay 31, 2021
  12. Atharva RaykarMay 31, 2021
  13. Christian CouderMay 31, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.