<div dir="ltr">Ok guys, thanks for the clarification.<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">2017-05-11 19:15 GMT+02:00 Till Wegmüller <span dir="ltr"><<a href="mailto:toasterson@gmail.com" target="_blank">toasterson@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello.<br>
<br>
Yes IPS uses precompiled Packages. However it does not distribute them as tarball archives but as seperate files. These fiels are Linked together by the manifests of a Package. Which is a Textfile describing all files, symlinks, mediators, etc. of a package.<br>
<br>
IPS itself does not use the source archive property. This is only relevant for OI-userland.<br>
<br>
OI userland is our version of Ports and also our Buidl system for packages.<br>
<br>
You can grab yourself the latest git revision of oi-userland and compile every package for yourself localy with it. Once you have installed build-essential package.<br>
<br>
Our Jenkins build servers do the same.<br>
<br>
Have a look at <a href="http://docs.openindiana.org/dev/userland/" rel="noreferrer" target="_blank">http://docs.openindiana.org/de<wbr>v/userland/</a> for more details on how to get started with oi-userland<br>
<br>
<br>
Greetings<br>
Till<br>
<br>
On 11.05.2017 13:28, Aurélien Larcher wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
<br>
On Thu, May 11, 2017 at 12:18 PM, Dariusz Sendkowski <<a href="mailto:dsendkowski@gmail.com" target="_blank">dsendkowski@gmail.com</a> <mailto:<a href="mailto:dsendkowski@gmail.com" target="_blank">dsendkowski@gmail.com</a>><wbr>> wrote:<br>
<br>
I guess that is exactly how it is done in OpenBSD. You have<br>
precompiled binaries, which you can fetch and install. You can also<br>
build them by yourself using OpenBSD ports system. If the original<br>
site is unavailable, the sources are downloaded directly from<br>
OpenBSD servers, for example:<br>
<br>
# cd /usr/ports/x11/libxdg-basedir/<br>
# make fetch<br>
===> Checking files for libxdg-basedir-1.2.0p0<br></span>
>> Fetch <a href="http://nevill.ch/libxdg-basedir/downloads/libxdg-basedir-1.2.0.tar.gz" rel="noreferrer" target="_blank">http://nevill.ch/libxdg-basedi<wbr>r/downloads/libxdg-basedir-1.<wbr>2.0.tar.gz</a> <<a href="http://nevill.ch/libxdg-basedir/downloads/libxdg-basedir-1.2.0.tar.gz" rel="noreferrer" target="_blank">http://nevill.ch/libxdg-based<wbr>ir/downloads/libxdg-basedir-1.<wbr>2.0.tar.gz</a>><span class=""><br>
ftp: connect: Connection refused<br>
>> Fetch <a href="https://ftp.openbsd.org/pub/OpenBSD/distfiles//libxdg-basedir-1.2.0.tar.gz" rel="noreferrer" target="_blank">https://ftp.openbsd.org/pub/Op<wbr>enBSD/distfiles//libxdg-basedi<wbr>r-1.2.0.tar.gz</a><br>
<<a href="https://ftp.openbsd.org/pub/OpenBSD/distfiles//libxdg-basedir-1.2.0.tar.gz" rel="noreferrer" target="_blank">https://ftp.openbsd.org/pub/O<wbr>penBSD/distfiles//libxdg-based<wbr>ir-1.2.0.tar.gz</a>><br>
libxdg-basedir-1.2.0.t... 100%<br>
<br>
Well, of course one can always clone oi-userland and build the<br>
packages by oneself.<br>
<br>
Anyway, I just wanted to know how exactly it is done in OI.<br>
<br>
Btw, I wanted to add libxdg-basedir to oi-userland but as you can<br>
see, the original site is not available any more.<br>
<br>
<br>
There is a mirror with archived tarballs at:<br>
<br>
<a href="http://dlc.openindiana.org/oi-userland/source-archives/" rel="noreferrer" target="_blank">http://dlc.openindiana.org/oi-<wbr>userland/source-archives/</a><br>
<br>
which can be used automatically if you set the EXTERNAL_ARCHIVE_MIRROR variable.<br>
<br>
I do not know what you mean exactly by "precompiled package".<br>
IPS is not based on "tarballs" and you can create pkg(5) archives for a given package version just by pkgrecv from the publisher, this seems a bit redundant.<br>
<br>
HTH<br>
<br>
<br>
regards,<br>
Darek<br>
<br>
<br>
<br>
2017-05-11 11:49 GMT+02:00 Nikola M <<a href="mailto:minikola@gmail.com" target="_blank">minikola@gmail.com</a><br></span>
<mailto:<a href="mailto:minikola@gmail.com" target="_blank">minikola@gmail.com</a>>>:<div><div class="h5"><br>
<br>
On 05/11/17 10:53 AM, Dariusz Sendkowski wrote:<br>
> Hi,<br>
><br>
> What happens when a component archive url points to a web resource<br>
> that is unavailable temporarily or, even worse, permanently? How does<br>
> it impact the package availability?<br>
><br>
> Are all these oi-userland components precompiled and stored somewhere<br>
> on the publisher server along with the sources? So when users install<br>
> some packages they fetch the precompiled packages regardless of the<br>
> corresponding archive urls availability?<br>
<br>
I asked that 3+ years ago and i think they are stored on Oi build<br>
servers, but not accessible from outside.<br>
<br>
It would be the best to always have all sources available at any<br>
time,<br>
so all source is fetched from OI servers, but it could be a<br>
project for<br>
itself to make upstream sources available locally on OI servers.<br>
<br>
Maintainers didn't like this, because fetching source archives from<br>
remote server is more simple for a building process.<br>
<br>
I also used to point out the legality of even distributing<br>
precompiled<br>
binaries before, without providing sources at any time. (and for any<br>
distributed binary).<br>
Having local store of source archives from the upstream projects,<br>
having all sources always available at OI site, would fix both<br>
legal and<br>
build problems and elevate problem if network source is not<br>
available.<br>
Maybe just make local source code archives on Oi servers,<br>
visible to all<br>
users?<br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
oi-dev mailing list<br></div></div>
<a href="mailto:oi-dev@openindiana.org" target="_blank">oi-dev@openindiana.org</a> <mailto:<a href="mailto:oi-dev@openindiana.org" target="_blank">oi-dev@openindiana.org</a><wbr>><br>
<a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="noreferrer" target="_blank">https://openindiana.org/mailma<wbr>n/listinfo/oi-dev</a><span class=""><br>
<<a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="noreferrer" target="_blank">https://openindiana.org/mailm<wbr>an/listinfo/oi-dev</a>><br>
<br>
<br>
<br>
<br>
-- <br>
---<br>
Praise the Caffeine embeddings<br>
<br>
<br>
______________________________<wbr>_________________<br>
oi-dev mailing list<br>
<a href="mailto:oi-dev@openindiana.org" target="_blank">oi-dev@openindiana.org</a><br>
<a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="noreferrer" target="_blank">https://openindiana.org/mailma<wbr>n/listinfo/oi-dev</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<wbr>_________________<br>
oi-dev mailing list<br>
<a href="mailto:oi-dev@openindiana.org" target="_blank">oi-dev@openindiana.org</a><br>
<a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="noreferrer" target="_blank">https://openindiana.org/mailma<wbr>n/listinfo/oi-dev</a></div></div></blockquote></div><br></div>