From owner-freebsd-ports-bugs@FreeBSD.ORG  Wed Jun 11 13:34:09 2014
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id AF3CE8FF
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 11 Jun 2014 13:34:09 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 95D562838
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 11 Jun 2014 13:34:09 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5BDY9Vo055731
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 11 Jun 2014 14:34:09 +0100 (BST)
 (envelope-from bz-noreply@freebsd.org)
From: bz-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 188971] [NEW PORT] revive port comms/sms_client : simple UNIX
 client allowing you to send SMS messages to mobile phones and pagers
Date: Wed, 11 Jun 2014 13:34:09 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports Tree
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: marino@FreeBSD.org
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-188971-13-MBQ36csRS8@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-188971-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-188971-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jun 2014 13:34:09 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188971

--- Comment #3 from John Marino <marino@FreeBSD.org> ---
Hi Chris,
As you surely have seen by my numerous running commentaries that these ports
have to meet today's standards.  Just reviving how they were back when they get
deleted is not nearly enough.

A couple of your ports were not staged (a sin big enough to immediately reject
nowadays)

Also check that it builds on both FreeBSD 10 as well as FreeBSD 8 and 9.  The
former have gcc as the base compiler, the later is of course, clang.  It's
common for ports to build on 8, 9 but not 10,11.  So it's worth checking that.

portlint helps a lot too.

-- 
You are receiving this mail because:
You are the assignee for the bug.