On Mon, 6 Jun 2016 13:28:13 +0200, parazyd wrote in message <20160606112813.ga11...@hansolo.lan>:
> On Mon, 06 Jun 2016, Lars Noodén wrote: > > > I've been messing around with building a live image and notice that > > it looks like there are a lot of different mirrors getting called > > into play. I was expecting the same mirrors to be used each time > > so I could populate my local cache on the first try and then use > > that cache on subsequent builds. Is there any efficient way to > > cache everything I access on the first try? I'm using squid3 right > > now but should I be using apt-cacher or apt-cacher-ng instead? > > > > If you're consistently making the same image each time, why not create > just a ready tarball you can extract each time you make an image? That > way you save your time and put less load on package mirrors. ..one way around that problem, is setting up your own package mirror on your own site, but nobody here at devuan wants you to do that, if I must rely on the absence of answers to my own mirror size etc questions here. ..my understanding is devuan mirrors can be mirrored with rsync scripts and then merged somehow with amprolla, pointing it to the Debian mirror of your choise, possibly putting it in the [DEBIAN] stanza in amprolla.conf.example, instead of host: ftp.de.debian.org and redirect: httpredir.debian.org. ..but first, roughly, how big (as in du -sch) is packages.devuan.org? -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
