Date: Sat, 18 Apr 2009 12:40:34 GMT From: Gerard Seibert <gerard@seibercom.net> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/133836: Update port: security/scamp Message-ID: <200904181240.n3ICeYtZ056943@www.freebsd.org> Resent-Message-ID: <200904181250.n3ICo1bQ003024@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 133836 >Category: ports >Synopsis: Update port: security/scamp >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Sat Apr 18 12:50:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Gerard Seibert >Release: FreeBSD-6.4 >Organization: seibercom.net >Environment: >Description: I submitted a new port. ports/133248: New Port: security/scamp a while ago. I realise that with the port's freeze, etc., it will be a while before the port is committed. That I fully understand. The has been an update to the scamp application. Should I wait until the port is actually released before submitting an update, or can I submit it now? Is there a better way to handle this? Since this port is not now in the official FreeBSD ports tree I do not know how to handle the situation. Thanks! >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200904181240.n3ICeYtZ056943>