Date: Fri, 27 Aug 1999 14:45:40 -0400 (EDT) From: Bill Fumerola <billf@jade.chc-chimes.com> To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> Cc: jack <jack@germanium.xtalwind.net>, Chris Piazza <cpiazza@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/net/ucd-snmp Makefile ports/net/ucd-snmp/files md5 ports/net/ucd-snmp/patches patch-ac ports/net/u Message-ID: <Pine.BSF.4.10.9908271431010.15163-100000@jade.chc-chimes.com> In-Reply-To: <199908271916.MAA56293@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 27 Aug 1999, Rodney W. Grimes wrote: > But you must care that ports/net/ucd-snmp is now a non-functional > port for many of the FreeBSD users. And if you don't care about > that, you _must_ care about your commit priv's. See below. > Changing one port and breaking another port that depends on it is > no different that changing one thing in /usr/src that breaks some > other thing, either go fix the other thing, work with the maintainer > to help them fix it, or back out your changes. This means the perl module needs updated, set to BROKEN, or removed if it no longer follows active development on it's dependencies. The snmp authors would be smart to bump their major library version as well, but again this is third party software we are dealing with, so it's not just as easy as fixing things across the board. > If the new rules don't make this clear, then they need more work... If breaking a minor perl module causes me to lose my commit privledges, then this project has bigger problems then unclear rules. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9908271431010.15163-100000>