Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Aug 1999 12:16:12 -0700 (PDT)
From:      "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
To:        billf@jade.chc-chimes.com (Bill Fumerola)
Cc:        jack@germanium.xtalwind.net (jack), cpiazza@FreeBSD.org (Chris Piazza), 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:  <199908271916.MAA56293@gndrsh.dnsmgr.net>
In-Reply-To: <Pine.BSF.4.10.9908271259110.15163-100000@jade.chc-chimes.com> from Bill Fumerola at "Aug 27, 1999 01:00:05 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
> On Fri, 27 Aug 1999, jack wrote:
> 
> > Are you aware that 4.0 was replaced after one day by 4.0.1 due to
> > bugs?  And that the p5-SNMP module won't compile due to header
> > file changes in ucd-snmp, and dumps core on a box with ucd-snmp
> > 4.x if built with ucd-snmp 3.x?
> 
> This anger should be directed at me.
> 
> When I looked at the UCD page, 4.0 was the only thing available.
> 
> Not to be rude, but I don't care if some perl script doesn't keep up
> with active development.

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.

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.

If the new rules don't make this clear, then they need more work...

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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?199908271916.MAA56293>