Date: Sun, 4 Nov 2007 14:31:44 -0600 From: linimon@lonesome.com (Mark Linimon) To: Miles Nordin <carton@Ivy.NET> Cc: freebsd-sparc64@freebsd.org Subject: Re: Doesn't anything work around here? Message-ID: <20071104203144.GA30608@soaustin.net> In-Reply-To: <oqr6j6arul.fsf@castrovalva.Ivy.NET> References: <ffg2gk$1n1r$1@nermal.rz1.convenimus.net> <200711011822.25884.linimon@lonesome.com> <fgk8ug$185e$3@nermal.rz1.convenimus.net> <20071104114811.GA19506@soaustin.net> <oqy7deatny.fsf@castrovalva.Ivy.NET> <472DF0DA.7090401@FreeBSD.org> <oqr6j6arul.fsf@castrovalva.Ivy.NET>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 04, 2007 at 11:38:26AM -0500, Miles Nordin wrote: > People working on the dominant architecture will say ``I don't have > a sparc64'' or ``I don't have a FreeBSD box,'' which means to them > more-or-less ``I don't have to worry about what I break here, because > after all, how could I?'' And thus, your recommendation is? [fwiw, Kris has probably done more to keep ports going on sparc64 than anyone else in the project, in terms of running package builds, identifying problems, emailing maintainers, and marking things broken when they don't install/deinstall cleanly. This is also true for the other architectures :-) ] The point that I'm trying to make is that it's easier to address specific problems than general ones. If you want things fixed, you're going to need to be proactive in identifying sources of breakage and notifying the people that caused them, whether that's via email or send-pr. mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071104203144.GA30608>