unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Eric Bavier <ericbavier@centurylink.net>
Cc: Quiliro Ordonez Baca <quiliro@riseup.net>, help-guix@gnu.org
Subject: Re: offline repo server
Date: Fri, 19 Jan 2018 15:01:47 +0200	[thread overview]
Message-ID: <20180119130147.GA1054@macbook41> (raw)
In-Reply-To: <20180117181249.0b8fb4a0@centurylink.net>

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

On Wed, Jan 17, 2018 at 06:12:49PM -0600, Eric Bavier wrote:
> On Wed, 17 Jan 2018 18:58:08 -0500
> Quiliro Ordonez Baca <quiliro@riseup.net> wrote:
> 
> > I am not sure if this has been asked before. But I live in a place where
> > there is no network link and I would like users to install different
> > softwares there.
> > 
> > Is it possible to have a machine connect to the net every so often so
> > that it updates all available substitutes (or source if substitutes are
> > not available)...and then take that machine to an offline site where
> > other machines use it to install all packages that users want?
> > 
> 
> I don't think we don't have anything out-of-the-box that would elegantly
> handle a use-case like this.  That being said, you should be able to
> hack something together.  I think a good place to start would be the
> recent work Ludovic did on 'guix weather', which queries substitute
> servers for availability of package substitutes.  You could base
> something off that which, instead of simply reporting statistics,
> actually builds the derivations: either the source derivation if a
> substitute is unavailable, or the package derivation.
> 
> Obviously, downloading substitutes and/or source for all
> packages could take quite a but of time, so you may instead want to
> limit to a manifest of the packages you're interested in.  But that
> could get more complicated because a package's source is "useless"
> unless you have sources or substitutes of the packages needed to build
> it, so you'd need to analyze the dependency tree a bit.
> 
> It's an interesting use-case.
> 
> Happy Hacking,
> `~Eric

The shell script I use on my aarch64 build machine is:
guix build --no-substitutes --no-grafts --keep-going $(guix package -A | cut -f1,2 --output-delimiter=@) --sources=transitive

Not related to caching sources but related to building all the packages,
I take off '--sources=transitive' and put on '--max-silent-time=1800' when
I'm= building everything.

I guess if you're not running it as a fully independant build server
then you wouldn't need the '--no-substitutes'


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

  reply	other threads:[~2018-01-19 13:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 23:58 offline repo server Quiliro Ordonez Baca
2018-01-17 23:59 ` Jalus Bilieyich
2018-01-18  0:12 ` Eric Bavier
2018-01-19 13:01   ` Efraim Flashner [this message]
2018-01-19 16:47 ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180119130147.GA1054@macbook41 \
    --to=efraim@flashner.co.il \
    --cc=ericbavier@centurylink.net \
    --cc=help-guix@gnu.org \
    --cc=quiliro@riseup.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).