Re: Avoid sending sources to offload servers

[Tomas Volf <~@wolfsden.cz>]

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

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---

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

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]