Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 05 Jun 2007 11:33:35 +0200
From:      Andrea Venturoli <ml.diespammer@netfence.it>
To:        "Timur I. Bakeyev" <timur@gnu.org>
Cc:        spil.oss@gmail.com, freebsd-ports@freebsd.org
Subject:   Re: [net/samba3] Upgrade to Samba 3.0.25a
Message-ID:  <46652DEF.1070709@netfence.it>
In-Reply-To: <20070605082244.GB22215@com.bat.ru>
References:  <5fbf03c20706050031p6f25d02cyae7a91593e40171a@mail.gmail.com> <20070605082244.GB22215@com.bat.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Timur I. Bakeyev wrote:

> I would like to stress, that after problems with the last Samba releases
> I decided to delay new port for at least one week to collect feedback
> from mailing lists and other sources, as well as from developers to see,
> if there are no fatal problems with the release. Unfortunately, with
> security updates we can't wait too long, thus 3.0.25 slipped into the
> ports collection, although it possibly shouldn't.

Ok, this is however not a fault in the way FreeBSD handles port.
This time it's samba itself that should be blamed (although I'm not 
recriminating here).



> I'm planning to ressurect net/samba3-devel port to put latest releases there,
> leaving net/samba3 for proven to work releases.

I don't think this issues are related.
If you feel you should, then obviously go ahead, but, as I see it, both 
3.0.25 and 3.0.25a would have gone into samba3, not samba3-devel.



Just my two e-cents :-)



  bye
	av.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46652DEF.1070709>