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.
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
