Date: Tue, 20 Jul 2010 17:25:52 -0400 From: Greg Larkin <glarkin@FreeBSD.org> To: Aiza <aiza21@comclark.com> Cc: freebsd-questions@freebsd.org Subject: Re: new jail utility is available. announcement. Message-ID: <4C461460.3090900@FreeBSD.org> In-Reply-To: <4C45FCE1.7010006@comclark.com> References: <4C452644.6060508@comclark.com> <20100720134205.3168f4f1@scorpio> <4C45EA1C.6070601@comclark.com> <20100720153209.74ec26e6@scorpio> <4C45FCE1.7010006@comclark.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Aiza wrote: > Jerry wrote: >> On Wed, 21 Jul 2010 02:25:32 +0800 >> Aiza <aiza21@comclark.com> articulated: >> >> >>> Like the announcement said the port is available at >>> http://sourceforge.net/projects/qjail/ >>> >>> And if you have ever submitted a new port for inclusion into the >>> freebsd ports system you would know that it takes months for it to >>> show up in the collection. >> >> Actually, I have submitted a few ports. I believe it averaged only >> approximately 10 to 14 days before they were officially committed to >> the ports tree. Updating them usually takes 10 days or less. >> >>> So you can wait till xmas or RELEASE 9.0 to come out for the port to >>> be in the ports collection or just fetch it form the development >>> project site. >> >> I guess I was just lucky I did not have to wait 6 months. I am >> assuming, perhaps incorrectly, that you might be the maintainer of this >> new port. What is the PR #? >> > There has been the normal pre RELEASE freeze on since xmas, that is why > no port activity is occurring right now. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=148777 Hi Aiza, Where did you get that information? Whoever told you that is mistaken. A large number of commits have entered the ports tree since the beginning of the year. Have a look at the ports CVS mailing list archive since December 2009: http://lists.freebsd.org/pipermail/cvs-ports/ The ports tree does go into a freeze or slush state around release times, but that doesn't completely stop commits either, mostly sweeping changes that affect a great number of ports or introduce some other incompatibility. Here's some more information: http://www.freebsd.org/doc/en/articles/committers-guide/ports.html#AEN1466 Hope that helps, and thank you for your new port, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMRhRg0sRouByUApARAqpqAJ9bvM5El5YXO0GjCfkmwaZwy4pXHQCgvuuc QNAOpT/EElnICj72S97QAuY= =jIkQ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C461460.3090900>