[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Avoid sending sources to offload servers
From: |
Simen Endsjø |
Subject: |
Re: Avoid sending sources to offload servers |
Date: |
Fri, 08 Nov 2024 22:08:32 +0100 |
User-agent: |
mu4e 1.12.7; emacs 29.4 |
Tomas Volf <~@wolfsden.cz> writes:
> Simen Endsjø <contact@simendsjo.me> writes:
>
>> I guess what I would like is at least that the sources for the builds
>> to be downloaded by the build server instead of transferred by my
>> system.
>
> I guess one limitation here is that the build server is not always able
> to download the sources. Some of my packages have source field like
> this:
>
> --8<---------------cut here---------------start------------->8---
> (source (local-file "/some/path/some/tar-0.0.0.tar.gz"))
> --8<---------------cut here---------------end--------------->8---
>
Good point. The packages in question doesn't have any local sources, but
I see your point.
It would also be impossible to know per-package what would be the most
optimal build plan. There's the input source size, the build time and
the output size to factor in. At least there's no magic going on here so
I can tweak things manually when needed.
> I can imagine having packages with sources that are for example
> available on LAN exposed HTTP server, and the build server does not have
> to be on the same network segment. I do not have use case for that yet,
> but I image other people might have.
>
> All of that is probably solvable, but I just wanted to point out that
> there are some edge cases in this that would require deeper thought.
>
> Tomas