From owner-freebsd-ports-bugs@FreeBSD.ORG  Sun Nov  2 06:28:12 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.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 7B1C8876
 for <freebsd-ports-bugs@FreeBSD.org>; Sun,  2 Nov 2014 06:28:12 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 61DE6DAF
 for <freebsd-ports-bugs@FreeBSD.org>; Sun,  2 Nov 2014 06:28:12 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sA26SCXi053934
 for <freebsd-ports-bugs@FreeBSD.org>; Sun, 2 Nov 2014 06:28:12 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 194702] [maintainer update] devel/p5-Connector to 1.15
Date: Sun, 02 Nov 2014 06:28:12 +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 Some People
X-Bugzilla-Who: svysh.fbsd@gmail.com
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-194702-13-WzVqHH3Vnl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-194702-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-194702-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-1
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: Sun, 02 Nov 2014 06:28:12 -0000

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

--- Comment #9 from Sergei Vyshenski <svysh.fbsd@gmail.com> ---
Please find attached a new fixed patch and new test logs.

You are absolutely right. Thank you very much.
Sorry about my previous ill contribution.
Sure it is me who is solely responsible for the quality of submitted pkg-plist.
But see how it happens:

- "make makeplist" generates pkg-plist with wrong "@dir ..." lines,
- "make check-plist" finds no pkg-plist issues,
- "portlint -AC" ver 2.16.1 finds no pkg-plist issues,
- poudriere testport ver 3.0.19 finds no pkg-plist issues

After updating of the ports infrastructure on Nov 1, 2014, "make makeplist" 
generates much more wrong "@dir ..." lines than 2 days ago. 

Looks like at the moment people are actively working on support of "@dir ...".
What would you recommend? 
Wait until it stabilizes by itself? 
Or submit a PRs against Mk infrastructure etc. right now?

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