[OpenIndiana-New-developers] #include <hello.h>
Kevin J. Woolley
kjw at javabunny.net
Mon Feb 28 06:42:47 UTC 2011
On 25 February 2011 08:18, Guido Berhoerster <gber at openindiana.org> wrote:
> sounds great, RPM packaging skills will be very useful. We have
> not yet started our own packaging project (OIAC) but if you're
> interested in packing additional software for OI right now it
> might make sense to integrate these packages into the
> spec-files-extra (SFE) project. Some OI community members
I've got an oi_148a VM set up on my main box, with a hardware
installation going onto a build box in the next day or two. The
latter box will host build zones, once I get zones figured out. :)
> have already gone that route and are e.g. working on Qt and
> PostgreSQL 9 packages within the SFE project. We are currently
> working on setting up an IPS repository with a selection of
> useful SFE packages.
Sounds good. The packages I'm interested in building aren't quite so
complex at this point, but I hope to get to that level reasonably
> More information about the SFE project can be found here
Bookmarked, and will document on the wiki if it's not already.
> Existing specfiles are here:
> Building SFE packages on OI is documented here:
I'll be installing the patched versions of SunStudio, etc. in the next
day or two. I assume it's non-trivial to make this work with a
regular release (such as 12.2).
> An open task here is to further automate builds on the OI
> infrastructure, e.g. to create a jucr-like setup where package
> updates automatically trigger a rebuild in a dedicated build
That's way over my head at this point, with my limited knowledge of zones.
> Basically you could contribute packages of software you use
> yourself or which you find useful or which people ask for on the
> mailinglist to SFE and we can then offer them through a new
> pkg.oi.o/sfe-unsupported IPS repo. Some packaging gaps I see are
> Postfix (experimental package is in SFE), Virtualbox, and
> Open/Libreoffice although it might be a good idea to start with
> something smaller first before tackling those.
I'll likely start with current versions of Ruby, Perl, and other dev
tools. Those are easy enough to build and test.
> Since you're already familiar with writing specfiles you could
> also help out by mentoring new developers interested in
> packaging, e.g. on this list or by offering a packagin lesson on
> IRC or as a turorial on the wiki.
Absolutely -- I'm a bit rusty, but I'm hoping it'll all come flooding
back. I'll likely write a few scripts to make things easier, such as
starting a specfile from scratch. Is there a standard/preference for
such scripts? My urge will be to write them in Perl, if not.
> If any of this sounds interesting to you, please let me know and
> I'll try to help you getting started.
Sounds good! I'm definitely interested. I'll let you know when I've
got the dev build environment ready (patched SS, cbe, etc.). At that
point I'll need a primer on setting up (and maintaining/removing/etc.)
build zones. From there I'll grab some existing specfiles and do test
builds. Assuming that all works, I'll get into the real guts of it.
More information about the New-developers