[OpenIndiana-discuss] OpenIndiana-discuss Digest, Vol 3, Issue 63
gary at genashor.com
Mon Oct 25 12:30:11 UTC 2010
On 10/25/10 8:00 AM, openindiana-discuss-request at openindiana.org wrote:
> Send OpenIndiana-discuss mailing list submissions to
> openindiana-discuss at openindiana.org
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> openindiana-discuss-request at openindiana.org
> You can reach the person managing the list at
> openindiana-discuss-owner at openindiana.org
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OpenIndiana-discuss digest..."
> Today's Topics:
> 1. Package repositories? (Joachim Pihl)
> Message: 1
> Date: Mon, 25 Oct 2010 07:46:45 +0200
> From: "Joachim Pihl"<joachim.pihl at sensordevelopments.com>
> To: openindiana-discuss at openindiana.org
> Subject: [OpenIndiana-discuss] Package repositories?
> Message-ID:<op.vk4ab7t3sev97k at joachim-lappis>
> Content-Type: text/plain; charset=iso-8859-15; format=flowed;
> Morning, all!
> I installed OpenIndiana a few weeks ago on my home file server, as a
> replacement for an old version of Solaris Community Edition after a bad
> case of on-disk corruption. I figure it is time to set up an MTA and all
> the associated bits + fetchmail.
> There are a few different Postfix and Dovecot packages floating around the
> net. The problem is telling which package is going to be maintained. Is
> the Blastwave repository actively maintained, and actually usable? Will
> the OpenIndiana project eventually include packages like the above?
Blastwave seems to be maintained adequately. The only problem I find
with Blastwave is that it requires the world to be brought in,
duplicating libraries already available as native packages to
/opt/csw/. If that doesn't bother you then blastwave will work fine.
My hope is that people (maybe you?) will step up to the plate and
provide missing spec files for wanted programs and that they become part
of the OpenIndiana native package set. There seems to be a discussion
at what the format for those packages will be for OpenIndiana which is
why I suggest doing the spec file route. I wouldn't think postfix
would have much problem in building on OpenIndiana, with a little work
I'm sure the svc files could be implemented to make it complete.
That said, I personally use a customized version of qmail (is there
anyone using a vanilla installation any more?) that uses spamdyke as a
front end. If I didn't have such a huge investment in the spam handling
infrastructure that I integrated into qmail, I would problem start fresh
with something like postfix. Then again, qmail has been working
flawlessly for me more than 20 years.
More information about the OpenIndiana-discuss