Date: Tue, 6 Mar 2012 16:30:18 GMT From: Michael Scheidell <scheidell@freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/165708: New port: net-p2p/tahoe-lafs Message-ID: <201203061630.q26GUINC078094@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/165708; it has been noted by GNATS. From: Michael Scheidell <scheidell@freebsd.org> To: <bug-followup@FreeBSD.ORG> Cc: Subject: Re: ports/165708: New port: net-p2p/tahoe-lafs Date: Tue, 6 Mar 2012 11:27:08 -0500 On 3/6/12 11:21 AM, bytestore wrote: > py-nevow marked as BROKEN but it is build and install normally... > You will need to submit a PR to patch py-nevow so that is it not marked broken. py-nevow is not maintained by anyone, so, if you mark it unbroken in a patch, you will also need to assume maintainership of the port, so, in your pr, you should include one patch that unbreaks py-nevow, and has your email address as maintainer. Further, you should subscribe to ports@ mailing list, and have them assist you in the correct way to use plist_sub variables in your pkg-plist, the correct use of PYSISTUTILS, and EGGINFO macros's, and correct way to install man pages. The new port as it stands does not follow FreeBSD standards. Start with your pr to take maintainership of py-nevow and unbreak it. While you are waiting for that to be committed, ask for help in ports@ for your tahoe-lafs port. -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203061630.q26GUINC078094>