[OpenIndiana-discuss] The Illumos pkgsrc project

[Mads Worsøe Duun]

Hi Dustin

Great to hear, any help is a great help, as this is so fare a one man
project.

I am not in favor of dictatorship, so decisions should be made by the
project members. Therefore I hope that we will have discussion about how
changes should be made to the pkgsrc tree. I vote for that we will maintain
our own tree, as we could commit changes faster. But of cause, changes
should also be sent back upstream. I guess this is something like what
DragonFlyBSD do.

Btw my bootstrap script does not support the Sun Studio compiler yet. I have
had much more success using the gcc compiler. I know that Studio will
generate better code, but it will involve much more pkgsrc hacking. My
script also first use an external gcc compiler to bootstrap pkgsrc, then
compile and switch to a "native" pkgsrc gcc compiler. The pkgsrc compiler
used as default in my script is gcc34, but you have the option to use gcc44,
and the too experimental compilers clang and pcc. This option will also
later support Sun Studio.

If you want to be official member of The Illumos pkgsrc project, please
register at http://www.illumos.org and let me know. Also please tell me what
kind of work you would like to help with.

Mads Worsøe Duun


2011/2/8 Dustin Marquess <dmarquess at gmail.com>

> I would like to help out if I can.  I've been using pkgsrc + Studio
> 12.2 exclusively on my OI servers, so I've already done quite a bit of
> hacking to get packages to compile.
>
> I assume any changes are going to be sent back upstream?  Sort of how
> the DFBSD pkgsrc stuff works?
>
> -Dustin
>
> On Tue, Feb 8, 2011 at 4:53 AM, Mads Worsøe Duun <mads at worsoe.dk> wrote:
> > 2011/2/7 Alasdair Lumsden <alasdairrr at gmail.com>
> >
> >> On 2 Feb 2011, at 19:30, Mads Worsøe Duun wrote:
> >>
> >> > *The Illumos pkgsrc project*
> >> >
> >> > I have created Illumos pkgsrc project at
> >> > http://www.illumos.org/projects/worsoe.
> >>
> >> Great stuff!
> >
> >
> > Somebody had to do it.
> >
> >
> >>
> >> > The is about making NetBSD's pkgsrc http://www.pkgsrc.org shine on
> >> > Illumos/Openindiana. Pkgsrc already work on Illumos/Openindiana, but
> >> really
> >> > need some love to make it shine. Below are some ideas of what is
> needed:
> >> >
> >> > *Script to bootstrap pkgsrc under Illumos/Openindiana (WIP)*
> >> > I already have a script to bootstrap pkgsrc, but some of it need to be
> >> > rewritten. It also need some more testing.
> >> >
> >> > *Pkgsrc patches for Solaris/Illumos pkgsrc*
> >> > A lot of packages will not build, or do not work very well on
> >> > Illumos/Openindiana, so patches need to be written. This is probably
> the
> >> > most needed and demanding task. Therefore I call for volunteers to
> help
> >> with
> >> > this. For commiting patches to pkgsrc, we can do one of too things:
> >> >
> >> > 1. Commit the patches to the official pkgsrc repo.
> >> > 2. Host our own repo, wich is in sync with the official repo
> >> >
> >> > With the second solution, we can have patches committed faster.
> >> >
> >> > *Pkgsrc2ips script*
> >> > Develop a script to convert pkgsrc to IPS packages. Creation of SVR4
> >> > packages is not needed, as a utility for this already exist in pkgsrc.
> >>
> >> I've already written a proof of concept for this.
> >>
> >> The biggest challenge is dealing with package dependencies - NetBSD
> allows
> >> strings as versions, such as 0.9.8g, 1.2rc2, 4.5alpha1 or whatever - and
> has
> >> some stupidly complicated (and as far as I'm concerned, stupid) method
> of
> >> comparing versions called dewey.
> >>
> >> So I decided in my proof of concept just to have dependencies based on
> >> package name, not version, and to leave dependencies to pkgsrc itself.
> >>
> >
> > The idea was to include a pkgsrc2ips function in that script that I
> already
> > got. But if you already got a proof of concept for this, there are no
> reason
> > to reinvent the wheel.
> >
> >
> >>
> >> > *Build bulk*
> >> > Creation of a build bulk system, to create binary packages (we also
> need
> >> a
> >> > host to provide binaries).
> >>
> >> OpenIndiana will happily host any repos, build zones or download sites
> (eg
> >> dlc.openindian.org) for this work. Please do join #oi-dev on
> >> irc.freenode.net to discuss this.
> >>
> >
> >
> >> Thanks!
> >>
> >> Alasdair
> >> _______________________________________________
> >> OpenIndiana-discuss mailing list
> >> OpenIndiana-discuss at openindiana.org
> >> http://openindiana.org/mailman/listinfo/openindiana-discuss
> >>
> >
> >
> > Thanks Alasdair, it's very nice to have your and Openindiana's support,
> and
> > I would be very happy to use openindiana.org as host for this project. I
> > have jointed #oi-dev (Worsoe) so we can discuss where to go from here.
> >
> > Regards,
> > Mads Worsøe Duun
> > _______________________________________________
> > OpenIndiana-discuss mailing list
> > OpenIndiana-discuss at openindiana.org
> > http://openindiana.org/mailman/listinfo/openindiana-discuss
> >
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>