Re: [oi-dev] Components archive url availability

Hello. 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. IPS itself does not use

Re: [oi-dev] Components archive url availability

On Thu, May 11, 2017 at 12:18 PM, Dariusz Sendkowski wrote: > I guess that is exactly how it is done in OpenBSD. You have precompiled > binaries, which you can fetch and install. You can also build them by > yourself using OpenBSD ports system. If the original site is

Re: [oi-dev] Components archive url availability

I guess that is exactly how it is done in OpenBSD. You have precompiled binaries, which you can fetch and install. You can also build them by yourself using OpenBSD ports system. If the original site is unavailable, the sources are downloaded directly from OpenBSD servers, for example: # cd

[oi-dev] Components archive url availability

Hi, What happens when a component archive url points to a web resource that is unavailable temporarily or, even worse, permanently? How does it impact the package availability? Are all these oi-userland components precompiled and stored somewhere on the publisher server along with the sources?