Date: Fri, 19 Jun 2015 23:05:54 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: james@elstone.net, freebsd-ports@FreeBSD.org Subject: Re: Maintainer Request for old port: net/udpsend Message-ID: <558413B2.50000@FreeBSD.org> In-Reply-To: <004701d0aa06$bf572730$3e057590$@net> References: <004701d0aa06$bf572730$3e057590$@net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/06/2015 6:38 AM, James Elstone wrote: > Hi FreeBSD Ports! > > > > I am writing in connection with the port [net/udpcast], historic details of > which I found here: > > > > http://www.freshports.org/net/udpcast > > > > I would like to take on this port, potentially host source code, and > actively maintain the port please! > > > > I am familiar with the FreeBSD porting process, but would like to understand > if the existing depreciated port can be resurfaced (as hinted on the strap > line comment on FreshPorts), or if I submit a new port via the usual > channels? > > > > I have a bit of an interest in restoring this utility to its former hay-day, > and don't agree with the original idea of making it deprecated: > > "Unfortunately, IPv4 multicast is very nearly a thing of the (distant) past. > None of these ports are maintained, almost all of them are not up to date > with the latest versions, most of which were released many years ago." > > > > I my humble opinion, in my context, I have a direct need to use this on the > FreeBSD platform for the foreseeable future, and am still keen to give back > more to the FreeBSD community. The port does not just support multicast, > but also supports one-way (not half-duplex) unicast udp file transfer which > is the element I am interested in. > > > > Guidance, wisdom and advice on this topic would be most welcomed please? > > > > Kind regards, > > > > James Elstone > > james@elstone.net > > +44 (0) 7775 633 330 > Hi James, The following should answer most, if not all of your questions on reviving the port: https://www.freebsd.org/doc/en/articles/committers-guide/ports.html#ports-qa-re-adding Regarding the post-readd process, I would recommend: 1) Create a new issue (Bugzilla). Use the summary: [RESURRECT] category/port: ${COMMENT} 2) In your (issue) description, provide the svn copy command you used (including args, revision, etc) so the person who takes the issue can follow the same process. 3) Attach a unified diff (svn diff, or diff -u) against the ports HEAD version for your changeset. As always: Don't forget to include (*as attachments*) QA results, at least: a) portlint -AC output b) poudriere testport (or bulk -t) output See: Porters Handbook, Section 9: Testing the Port: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing.html If you need help, we have #bsdports on Efnet, or #freebsd-ports on freenode IRC to assist. Thank you for taking the initiative, getting in touch and contributing to FreeBSD :) -- ./koobs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?558413B2.50000>