News for hackers. Stuff that matters.
Re:Eden by 411111111111111 on Tuesday April 12, 2022 @05:14PM (#31008303)
> Build system integration

It would be a game changer if any SCM actually manages to achieve this without needing multiple developer teams just for maintenance.

That would probably break gits current dominance within a relatively short timeframe... But I don't think it'll happen within the foreseeable future,

Re:Eden by avar on Tuesday April 12, 2022 @05:59PM (#31008759)
If you want an SCM with direct build system integration there's always GNU make with its support for RCS :)

More seriously, can you describe what "build system integration" would look like? Basically like what GNU make does with RCS? I.e. considering the SCM "files" as sources.

How would such a system build a dumb tarball snapshot?

Re:Eden by xmcqdpt2 on Tuesday April 12, 2022 @08:34PM (#31009881)
At my work we have such a system for our monorepo. Basically for each compilation unit (basically subdirectories), it takes the compilation inputs and flags etc and checks them against a remote cache. If it matches, it just pulls the results (binaries but also compiler warnings) from the remote instead of compiling anything. A new clean build is made every few commits to the main branch to populate the cache.

In practice it means that if I clone the repo and build it doesn't ever invoke the compiler, so that it takes only a few minutes instead of an hour.

Bazel has a similar system but I haven't used it myself,

https://docs.bazel.build/versions/main/remote-caching.html

Re:Eden by avar on Wednesday April 13, 2022 @04:44AM (#31012441)
That seems really useful, but how is this different from what ccache and various other compilation caches that cache things as a function of their input do?

The GP talks about "build system integration" being "a game changer", and I can see that being a useful thing for e.g. "priming" your cache, but that's surely just a matter of say:

    ccache-like-tool --prime $(git rev-parse HEAD:)
I.e. give it an arbitrary "root" key and it would pre-download the cached assets for that given key, in this case the key is git-specific, but it could also be a:

    find -type f -name '*.[ch]' -exec cat {} \; | sha1sum | cut -d' ' -f1
Or whatever.
Re:Eden by maccard on Wednesday April 13, 2022 @05:48AM (#31012783)
> how is this different from what ccache and various other compilation caches that cache things as a function of their input do?

Vertical integration, basically. There is value in these things working, and working well. As an example of the issues with ccache etc, I've yet to find a compilation cache that works well on windows for large projects.

Re:Eden by xmcqdpt2 on Wednesday April 13, 2022 @07:40PM (#31021686)
I've never worked on a project with a large remote ccache but I would guess it would be pretty much the same yes.

The "automation" of our in-house system is what really makes the difference but then again we have a team of developers that focus on tooling so it's not so much automated as it is maintained...