Re: [oi-dev] Can I still install older perl and python?

Hi. On 12.05.2017 02:14, Gordon Ross wrote: I've been trying out the latest OI build, and most things look great! (Thanks to everyone who helped.) However, I have some 3rd party stuff that wants older versions of perl (5.10.0, 5.16) and python (2.6) and I can't figure out how to get pkg to let

Re: [oi-dev] Discussing maintainers visibility in oi-userland

On 11.05.2017 22:13, Peter Tribble wrote: On Thu, May 11, 2017 at 6:56 PM, Aurélien Larcher < aurelien.larc...@gmail.com> wrote: The question raised is whether we should formalize a maintaining process for some important components or groups of components. At some point I joked about a

Re: [oi-dev] Discussing maintainers visibility in oi-userland

À Jeudi 11 mai 2017, Adam Števko a écrit : > Hello, > > I would like to keep the status quo in this. We don’t have formal maintainers > and basically every change to the package/component is reviewed by relevant > person (me/alp/aurelien//jimklimov/wacki/agnar). I would really like to see >

[oi-dev] Can I still install older perl and python?

I've been trying out the latest OI build, and most things look great! (Thanks to everyone who helped.) However, I have some 3rd party stuff that wants older versions of perl (5.10.0, 5.16) and python (2.6) and I can't figure out how to get pkg to let me install those along side the current ones

Re: [oi-dev] Discussing maintainers visibility in oi-userland

Hello, I would like to keep the status quo in this. We don’t have formal maintainers and basically every change to the package/component is reviewed by relevant person (me/alp/aurelien//jimklimov/wacki/agnar). I would really like to see this list to grow and reach the phase that we need to

Re: [oi-dev] exiv2 broken?

Sorry, I haven't been able to help here. I am quite busy with private things at the moment. Regards, Andreas Am 11.05.17 um 13:42 schrieb Carsten Grzemba: On 10.05.17 07:21, *Carsten Grzemba * wrote: On 09.05.17 23:16, *Adam Števko * wrote:

Re: [oi-dev] Discussing maintainers visibility in oi-userland

On Thu, May 11, 2017 at 6:56 PM, Aurélien Larcher < aurelien.larc...@gmail.com> wrote: > > The question raised is whether we should formalize a maintaining process > for some important components or groups of components. > > At some point I joked about a campaign going like "Adopt a package". >

[oi-dev] Discussing maintainers visibility in oi-userland

Hi, following an offlist discussion with Darek, he asked: Is there any list of components, which have maintainers? > This case shows that some components need maintainers. I guess some people > decide whether a component needs a maintainer or not. > I explained that there are no officially

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] Volunteer needed to take over the Twitter feed

On Wed, May 10, 2017 at 5:05 PM, Cezary Podbilski via oi-dev < oi-dev@openindiana.org> wrote: > Aurélien, > > > Awesome, sounds good! Please brief away > Very good! Let us handle the details off-list. Kind regards Aurelien > > > Regards > > > Cezary > > > À Mercredi 10 mai 2017, Cezary

Re: [oi-dev] exiv2 broken?

On 10.05.17 07:21, Carsten Grzemba wrote: > > > > On 09.05.17 23:16, Adam Števko wrote: > > > > Hey, > > > > yes and possibly submit a fix, please. > > > > Thanks, > > Adam > > > > > On May 9, 2017, at 7:56 PM, Andreas Wacknitz

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?