4 ms·

But at which point would they stop being persisted? Surely not right after the build completing, so.. requiring manually running some "ok now clean redownloadab

by dzaima 3y ago

But at which point would they stop being persisted? Surely not right after the build completing, so.. requiring manually running some "ok now clean redownloadable dependencies" command (noone's gonna bother, and at that point a regular clean makes more sense)? adding a cron job on my system (please don't)? on some other build command invocation after some time (will likely never happen)? Most of your suggestions here make sense under the assumption that the project in question is one whose development I participate in/with some regularity engage with, but that simply isn't the case for most projects a given person may have some desire/need to build from source.

charcircuit 3y ago
>But at which point would they stop being persisted? You can either manually run the cleanup after the build or when you need free space. Alternatively a systemd timer that deletes old stuff that hasn't been accessed in weeks would work too. The same issue exists even only the system toolchain is used. There will me gigabytes of dependencies or object files that aren't needed taking up space. This is a problem of all dependencies. Toolchain dependencies are not special.
- dzaima 3y ago
  > There will me gigabytes of dependencies or object files that aren't needed taking up space. Among the couple dozen things I've got built from source, most have their object files sum up to less than the 117MB of a libLLVM-15.so.1, and if not, are only slightly larger (200-300MB). (and, as for the topic in question, maybe only one downloaded its own toolchain, and everything else freely allowed me to give a local gcc or clang in 'CC='/'CXX='). I think a build of all targets of QEMU is the only significantly larger thing I have (1.9GB of binaries, 2.1GB of object files). > Alternatively a systemd timer that deletes old stuff that hasn't been accessed in weeks would work too. Besides being awful (why does a build system need to even know about systemd?!?!!? much less make a semi-permanent addition), that also would fail if I moved the build directory to somewhere else (which, granted, would probably mean a clean would be needed to rebuild, but I will not care when I'm moving all of my git clones from one drive to another).
- mort96 3y ago
  So you want deep integration between the build system and systemd now. I'm happy you're not responsible for most of the FOSS projects I compile.

by dzaima 3y ago

charcircuit 3y ago

>But at which point would they stop being persisted? You can either manually run the cleanup after the build or when you need free space. Alternatively a systemd timer that deletes old stuff that hasn't been accessed in weeks would work too. The same issue exists even only the system toolchain is used. There will me gigabytes of dependencies or object files that aren't needed taking up space. This is a problem of all dependencies. Toolchain dependencies are not special.

dzaima 3y ago
> There will me gigabytes of dependencies or object files that aren't needed taking up space. Among the couple dozen things I've got built from source, most have their object files sum up to less than the 117MB of a libLLVM-15.so.1, and if not, are only slightly larger (200-300MB). (and, as for the topic in question, maybe only one downloaded its own toolchain, and everything else freely allowed me to give a local gcc or clang in 'CC='/'CXX='). I think a build of all targets of QEMU is the only significantly larger thing I have (1.9GB of binaries, 2.1GB of object files). > Alternatively a systemd timer that deletes old stuff that hasn't been accessed in weeks would work too. Besides being awful (why does a build system need to even know about systemd?!?!!? much less make a semi-permanent addition), that also would fail if I moved the build directory to somewhere else (which, granted, would probably mean a clean would be needed to rebuild, but I will not care when I'm moving all of my git clones from one drive to another).
mort96 3y ago
So you want deep integration between the build system and systemd now. I'm happy you're not responsible for most of the FOSS projects I compile.