Date: Thu, 28 Jul 2005 16:31:08 -0500 From: Paul Schmehl <pauls@utdallas.edu> To: ports@freebsd.org Subject: Re: New port with maintainer ports@FreeBSD.org [was: Question about maintainers] Message-ID: <47ECFCB8BE498CEAB57757D7@utd59514.utdallas.edu> In-Reply-To: <790a9fff050728142793c7588@mail.gmail.com> References: <C3B81AFDB8A5DFB5AB566CC4@utd59514.utdallas.edu> <42E81050.7090305@cs.tu-berlin.de> <66A226C3557B48ED535E3FED@utd59514.utdallas.edu> <20050727230523.GB54954@isis.sigpipe.cz> <20050728154248.GA943@zi025.glhnet.mhn.de> <20050728164111.GA66015@isis.sigpipe.cz> <42E917BA.10406@exit.com> <FACB47A35BF38243FBC04766@utd59514.utdallas.edu> <790a9fff050728142793c7588@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--On Thursday, July 28, 2005 16:27:21 -0500 Scot Hetzel <swhetzel@gmail.com> wrote: > > You wouldn't have to take on an additional challenge if one of the > dependant ports is broken for a port your creating, what you could do > is: > > 1. if MAINTAINER is not ports@, send a message to the MAINTAINER of the > port 2. Send a PR for the port with a description of the breakage and a > build.log containing the error > 3. Same as 2, but you also correct the problem in the port, and > include a Patch in the PR > 4. Same as 3, and also ask to take maintainership if MAINTAINER is > ports@. 5. Send a message to ports@ to see if anyone else had a problem > with that port, and a if they have a solution > Thanks, Scot. That's helpful to know. I wasn't aware, for example, that anyone could submit PRs for a broken port. Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/ir/security/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47ECFCB8BE498CEAB57757D7>