[belenix-dev] Fwd: [indiana-discuss] How to update Opensolaris 2008.05 to build 90

[Ananth Shrinivas]

Updating the core ON packages periodically and hosting them on our
repository is a good idea. But I see some unknowns that need to be resolved:

Say we release 0.7.1 with build 89. When ON moves to 90, we publish a new
set of packages that includes the kernel, libc and potentially *all* new ON
packages. Now I am a BeleniX user who wants to update my say,
python-xmlparser package and assume that it depends on SUNWlxml. And
SUNWlxml in turn depends on SUNWcsl which might depend on SUNWckr etc.. and
so on. I *could* potentially end up moving quite a bit of my system binaries
including the kernel to build 90.

The question is do we want this to happen ? There might be people who want
to stay at some stable kernel level and there might be others who don't want
to pull so much of data to just update some userland package. Note that this
would even happen when you do a new installation of some package.

>From the IPS point of view, this happens because publishing a new version of
a package creates a hierarchy and dependencies are always satisfied by
installing the latest version of packages.

To draw a parallel with linux, the kernel and glibc get updated only every 6
months or so. In our case, it could be every 15 days.

I am not against the idea of publishing newer ON builds. In fact, I think
that and hosting repositories of bleeding edge stuff on opensolaris.org -
like say the Crossbow bits or the In-Kernel ext3 implementation [1] would be
an awesome idea. But we would need to work out policies - maybe multiple
repositories or maybe pkg naming conventions - to make sure the regular joe
user doesn't see much impact.

[1] - http://www.opensolaris.org/os/project/ext3

Ananth

On Sat, May 24, 2008 at 10:55 PM, Moinak Ghosh <moinakg at gmail.com> wrote:

> Hi Folks,
>
>   I seem to see an idea here. The BeleniX pkg repo (once it is setup)
> should be updated to newer builds as and when they are available.
> Experimental project packages should also be readily made available.
>
> Regards,
> Moinak.
>
> ---------- Forwarded message ----------
> From: Dirk Steinberg <dws at steinbergnet.net>
> Date: Sat, May 24, 2008 at 10:39 PM
> Subject: [indiana-discuss] How to update Opensolaris 2008.05 to build 90
> To: indiana-discuss at opensolaris.org
>
>
> Hi,
>
> i'd like to follow Opensolaris development closely for updates
> to ZFS, iSCSI, COMSTAR, etc.
>
> Previsously I did that based on SXCR, BFU'ing once in a while
> to biweekly onnv builds or even to weekly snapshots.
>
> Well, BFU is a terrible way to do package upgrades, and
> "Indiana" was described as the new fast-moving Opensolaris
> distribution, and "pkg" looked much better than BFU.
> So I went ahead and installed Opensolaris 2008.05.
>
> But now I am stuck at build 86 and struggeling to see how
> to update to newer builds, presently that would be onnv_90.
>
> What authority do I have to point pkg to, or where do I find
> all the osol builds in pkg-digestable format?
>
> If binary packages do not exist, how can I build them myself?
>
> And what about the other projects, like ZFS crypto and such?
> All of them seem to just offer BFU bundles, not pkg authorities.
>
> Is it possible to BFU an Opensolaris 2008.05 base? (Besides the point that
> this would of course screw up all the pkg versioning...)
>
> What about the other way around: Is it possible to install additional
> pkg packages on top of a SXCR base?
>
> Still a little confused... :-)
>
> Thanks for any helpful pointers.
>
> Cheers,
> Dirk
> --
>
> This message posted from opensolaris.org
>
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080524/847203b8/attachment.html