Date: Thu, 6 Apr 2000 19:12:10 -0400 From: Will Andrews <andrews@technologist.com> To: Brandon Fosdick <bfoz@glue.umd.edu> Cc: Keith Ray <rayk@sugar-land.spc.slb.com>, freebsd-ports@FreeBSD.ORG Subject: Re: How long until a port is committed? Message-ID: <20000406191210.B94924@argon.blackdawn.com> In-Reply-To: <38ED13B5.F30767B4@glue.umd.edu>; from bfoz@glue.umd.edu on Thu, Apr 06, 2000 at 06:46:13PM -0400 References: <4.3.1.2.20000406161429.00ae75b0@163.188.48.51> <38ED13B5.F30767B4@glue.umd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 06, 2000 at 06:46:13PM -0400, Brandon Fosdick wrote: > I'm not a commiter but from what I've seen the results vary a lot > depending on many things. I had one port that was commited the same day > and another one that took weeks. I think it mostly depends on how busy > the committers are and how complicated your port is. It also depends on how much of the legwork you've done in regards to the port. If you check with Satoshi on whether the port should go in the category you've selected, that's a real plus. If you check your port with portlint, then all the better. If you check the website (if there is one) relating to your program, then thats good. If you check with Satoshi on whether a repo-copy will be needed (and even convince him to do it before somebody imports your port), that's another plus. :-) There's a lot of things you can do to ensure speed in committing ports. Doing all the legwork for committers is one of the best ways. :-> -- Will Andrews <andrews@technologist.com> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000406191210.B94924>