[csw-maintainers] Cherry-picking unstable packages

[Maciej (Matchek) Bliziński]

2012/11/29 Guillaume Rousse <guillomovitch at opencsw.org>:
> My dilemn is that those packages are currently in the "unstable" catalog,
> whereas my solaris hosts are currently configured to use tje "testing"
> catalog, so I can't install them easily through pkgutil. I see the following
> strategies:
>
> 1) wait for those packages to be available in "testing"

If you want to keep using the
http://mirror.opencsw.org/opencsw/testing/ (or similar, on another
mirror), this will take at least half a year, see [1].

> 2) manually pull and install those packages from the mirror

Requires resolving dependencies by hand, could cause problems because
of incompatible package versions. Can be tricky and painful.

> 3) switch all those hosts to use "unstable"

Probably not a good thing for production hosts to pull directly from
unstable. You could add your own staging solution, where you mirror
the unstable catalog, and sync it when you choose to.

> I don't have any ETA for 1, and 3 seems quite hazardous, so I think 2 is the
> best compromise. However, if pkg-add

By "pkg-get", did you mean pkgutil?

> is the functional equivalence of rpm in
> linux world, I fear I'll have to resolve dependencies manually... Is there
> any better tools to achieve it ?

4) switch to the kiel catalog

The kiel catalog is now what dublin used to be - it gets periodic
updates from the unstable catalog, so you're likely to avoid temporary
problems when a package is uploaded, then detected as problematic, and
fixed or rolled back. The kiel catalog will eventually become the
testing catalog, but it's not at the moment, and will not until dublin
becomes the stable catalog.

[1] http://www.opencsw.org/2012/11/roadmap-for-2013/