[oi-dev] OI project reboot required

Andrzej Szeszo aszeszo at gmail.com
Sun May 12 11:11:48 UTC 2013


Hi Piotr

I made some choices without consulting anyone but it allowed me to get
something set up in a short period of time.

oi_151a8 is based on sfw-gate, that's correct. Milan built JDS against
oi_151a8.
Because oi_151a8 and JDS bits were already available I thought it would be
a shame to not to include them in the repo I was preparing.

/experimental, oi-build, illumos-userland didn't really took off. I know
they exist but it would take time to figure out in what shape the binary
package repos are. I thought it would be a better idea to start fresh in
terms of binary packages. Build recipes however we should reuse. The github
repo currently does not produce anything else other than few meta-packages.
Build recipes from oi-build or illumos-userland can be added to the tree
and should just work. There is an option of enabling disabled Oracle
provided packages as well.

This time I wanted to keep things really simple. There is single publisher
now - 'openindiana.org' - but pointing at different repo. And single source
repo -  https://github.com/OpenIndiana/oi-userland. Any fixes or additions
should be made in the github repo.

In terms of fixes to the packages that came from SFW , I recommend using
equivalent package from one of the userland-style repos. The idea is to not
to have to compile SFW or run distro-importer ever again :)

Correct me if I am wrong, but illumos-userland is dead. I don't see a point
using it directly. Build recipes should be borrowed from it though :)

I have heard about libffi. Not sure what the problem is. It doesn't look
like it would be difficult to provide userland build recipe for it in case
we need an updated version.

Andrzej




On 12 May 2013 12:09, Piotr Jasiukajtis <estibi at me.com> wrote:

> Andrzej,
>
> oi_151a8 is still based on sfw-gate, wouldn't be better to resurrect
> /experimental which was based on illumos-userland?
>
> To me it was hard to manage different IPS versions along with the build
> environments/zones because some were based on /experimental while my main
> host was /dev.
> Another source of confusion are 3 different source repositories: sfw,
> oi-build and illumos-userland. Which one to use if I need a new package on
> my production systems? and no, I don't want to touch SFW anymore :)
>
> Maybe create another version based on illumos-userland in the /dev let say
> oi_152a1 or something?
>
>
> Btw, someone mentioned about some libffi issues on oi_151a8.
> I barely checked that and it seems pkg and python do work but I don't know
> what the issue was. Is that fixed?
>
> Thanks for doing that :)
>
> --
> Piotr Jasiukajtis
>
> On May 12, 2013, at 10:30 AM, Andrzej Szeszo <aszeszo at gmail.com> wrote:
>
> > Hi All
> >
> > Apologies for a delay. Some things are set up now.
> >
> > New IPS repository is up: http://pkg.openindiana.org/hipster/. It is a
> clone of the /dev repo + oi_151a8 bits from Jon Tibble and JDS bits from
> Milan Jurik merged in. Run commands below to update your system. You can
> ask Jon Tibble where the name of the repo came from :)
> >
> > pkg set-publisher -O http://pkg.openindiana.org/hipster/ openindiana.org
> > pk install -v pkg://package/pkg
> > pkg update -v
> >
> > Latest Oracle userland hg repo was converted to git and uploaded to
> https://github.com/OpenIndiana/oi-userland/. Most of the components were
> masked and don't build by default. I have only unmasked few meta packages
> to test if things build/publish correctly.
> >
> > Quick Jenkins instance that automatically builds packages and publishes
> them directly to http://pkg.openindiana.org/hipster/.
> >
> > To start hacking, fork a repo on github, make your changes (unmask
> packages, add new ones) and submit pull request. If you are an existing
> contributor, give me a shout and I will give you direct access to the repo.
> >
> > Please let me know if you have any questions.
> >
> > Let's see if the process works out.
> >
> > Kind regards,
> >
> > Andrzej
> >
> >
> >
> > On 11 May 2013 18:28, Andrzej Szeszo <aszeszo at gmail.com> wrote:
> > Hi Alasdair
> >
> > I would like to try setting up a repo on github, give trusted people
> direct access and support pull requests from independent developers. And
> then have jenkins publish packages incrementally to publicly accessible
> repository. In theory, it should only take few minutes from a push to a
> published package in a repo.
> >
> > It is a variation on the process which was tried earlier. I think it
> might work this time.
> >
> > I did some prep work last night. Will try to have something usable by
> others later tonight.
> >
> > Cheers,
> >
> > Andrzej
> >
> >
> >
> >
> > On 10 May 2013 14:04, Alasdair Lumsden <alasdairrr at gmail.com> wrote:
> > Andrzej,
> >
> > Your vision is pretty much the same one I had. The challenge is this:
> >
> > "Existing releng process and contribution process prevent anything from
> happening though. I would like to help to change that."
> >
> > How?
> >
> >
> > On Fri, May 10, 2013 at 12:54 PM, Jim Klimov <jimklimov at cos.ru> wrote:
> > On 2013-05-10 02:19, Garrett D'Amore wrote:
> > There is little "commercial future" in the desktop for Linux
> distributions as well yet almost all of them have a graphical desktop.
> >
> > I would be entirely *unsurprised* if distro vendors like RedHat and
> Oracle simply *ditched* their desktop support at some point in the future
> -- its clear to me at least that folks aren't running those distros on the
> desktop.
> >
> > Well, Oracle does provide and promote SunRays, and while admittedly most
> of their market targeting is about VDI and access to virtual
> > Windows desktops, there are many requests on the SRSS mailing list
> > about adding support for server-side Ubuntu as the SRSS terminal
> > server, because certain apps only exist for Linux and tunneling
> > of connections makes their graphics lag, and RHEL/OEL/Solaris
> > desktops are argued to be not so user-friendly (I have no opinion
> > on this, to me X11 is a means to display more characters on screen
> > than possible in a text mode).
> >
> > Not that Oracle seems to care to address that demand, at least
> > publicly - just recently they began supporting versions 6 of RHEL
> > and OEL as server-side Linuxes. But there is certain demand for
> > non-MS/Apple desktops, and one linked to commercial interest as
> > well. I am not sure if OI/illumos can ride that tide, though.
> > Maybe with some other terminal client technologies (ThinLinc,
> > Wyse, etc)?..
> >
> > //Jim
> >
> >
> >
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > http://openindiana.org/mailman/listinfo/oi-dev
> >
> >
> >
> > --
> > Alasdair Lumsden
> >
> > http://www.everycity.co.uk
> >
> > EveryCity Managed Hosting
> > Studio 18 Bluelion Place
> > 237 Long Lane, London, SE1 4PU
> >
> > general: 020 7183 2800
> > support: 020 7183 2801
> > email: al at everycity.co.uk
> >
> > Every City Limited
> > Registered in England and Wales, No. 5689474 Registered Office: Roper
> > Yard, Roper Road, Canterbury, CT2 7EX
> >
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > http://openindiana.org/mailman/listinfo/oi-dev
> >
> >
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > http://openindiana.org/mailman/listinfo/oi-dev
>
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20130512/997c92be/attachment-0005.html>


More information about the oi-dev mailing list