HEADS UP: change in ports rc.d script behaviour

David O'Brien dev-null at NUXI.com
Sat Jul 24 12:57:09 PDT 2004

On Sat, Jul 24, 2004 at 09:35:15PM +0200, Tobias Roth wrote:
> guys, this is -CURRENT. it's normal that some changes break other things.
> what's the point in complaining this breaking some ports? if you run
> -CURRENT on a production box, you usually are aware of what you are
> risking.
> also, the time chosen for this upgrade is as good as any. in fact, i even
> think this is a good timing, since 5.3 is getting closer.

> and it's not  mikes responsibility to fix every port this breaks.

I'm not so sure -- I often hear complains from Kris about commits in
/usr/src that break ports.  It seems implied reponsabilty on the /usr/src
committer to go help fix the ports.

I've seen bsd.port.mk changes held back that broke less ports than this
change, simply because the change caused any breakage.
-- David  (obrien at FreeBSD.org)

More information about the freebsd-ports mailing list