From owner-freebsd-python@FreeBSD.ORG Sat Sep 6 10:42:50 2014
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
Delivered-To: python@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 32335F24
for <python@FreeBSD.org>; Sat, 6 Sep 2014 10:42:50 +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 F3651147A
for <python@FreeBSD.org>; Sat, 6 Sep 2014 10:42:49 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s86AgnQn041419
for <python@FreeBSD.org>; Sat, 6 Sep 2014 10:42:49 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: python@FreeBSD.org
Subject: [Bug 193313] [NEW PORT] www/py-wsgidav: wsgi implemented DAV
Date: Sat, 06 Sep 2014 10:42:50 +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: needs-qa
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: koobs@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: python@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-193313-21822-VCG2fzb3l6@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193313-21822@https.bugs.freebsd.org/bugzilla/>
References: <bug-193313-21822@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-python@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-python>,
<mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python/>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>,
<mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Sep 2014 10:42:50 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193313
Kubilay Kocak <koobs@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-qa
--- Comment #8 from Kubilay Kocak <koobs@FreeBSD.org> ---
(In reply to Jingfeng Yan from comment #4)
> (In reply to Kubilay Kocak from comment #3)
> > Thanks for your submission Jingfeng.
> Thank you for your reviewing.
You're welcome
> > Additional review items:
> >
> > * LICENSE_FILE is missing
> LICENSE_FILE seems not to be mandatory and some py modules do not have full
> text of license. For example, zope213... The only LICENSE info only be
> carried in PKG-INFO file.
Include it if the distribution files contain a standalone license file. If not
that's fine
> > * Is there a reason the tests directory cant remain?
> Some of python modules have test directory. When install, it first detects
> __init__.py exists in the tests directory (some other modules have installed
> tests). The other thing that I don't understand well, all the python
> modules' tests directory install to the same location, and is there any way
> to avoid name conflict?
> __init__.py is place holder in most of cases (but it could do something,
> too). How about other file names. If there is better way to keep the tests
> directory, I will follow.
Certainly clean up if the python package installs conflicting files. It's
prudent to create issue reports for these things upstream, so that authors can
learn to improve their packaging methods, and we can also leverage test
functionality.
One last thing,
When you're providing updates to previous submitted attachments, remove all
attachments except for the latest (and complete) versions you want to be
reviewed and committed.
The diff of the last requested changes is not needed, only the latest version.
--
You are receiving this mail because:
You are the assignee for the bug.