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

Re: Proposal and Validation of Git Compile

From
RReto <reto@labrat.space>
Date
Mar 13, 2024, 08:08 UTC
Message-ID
<52ot6dibj4o5mhgsmxpa5r2hkllxrwwhf2azgkvtpaopldi2pg@5etkc4r3eunm>
In-Reply-To
<CABCSMAeySCkg6A1R3PUwrHyWRKMKnBH3OGnd8OtX-OpsGoOTkQ@mail.gmail.com>
On Tue, Mar 12, 2024 at 11:24:17PM -0400, Bhargav Vishnu wrote:
> - A large amount of similar duplicate codes are written by authors in
> different personal projects like utilities. These must be made reusable.
> Eg: Code on a gist is copied into every repository, why not create and use
> the gist itself as it also has versioning?

You are re-inventing the normal dependency packaging of the languages, poorly. We already have language specific ways (npm, pip, cargo, go get...) for almost all ecosystems. They have version controlled and checksumed dependency resolution and are actually aware what's needed (binary vs source distribution, additional deps etc).

I don't see why you'd want your version control system to do it, rather than using what already exists.

"Code on a gist is copied into every repository" is what we call a library, so package it up and pull it down with your favorite dependency management tool during the project build.

Previous: Bhargav VishnuNext: Konstantin Khomoutov
Message 2 of 3 in “Proposal and Validation of Git Compile”
  1. Bhargav VishnuMar 13, 2024
  2. RetoMar 13, 2024
  3. Konstantin KhomoutovMar 13, 2024

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.