Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Mar 1999 21:15:00 -0700
From:      Brett Glass <brett@lariat.org>
To:        Brett Taylor <brett@peloton.physics.montana.edu>
Cc:        freebsd-advocacy@FreeBSD.ORG
Subject:   Re: bsd vs. linux and NT chart
Message-ID:  <4.1.19990302210310.009fccf0@localhost>
In-Reply-To: <Pine.BSF.4.05.9903022006060.21648-100000@peloton.physics.m ontana.edu>
References:  <4.1.19990302181055.00ad67a0@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
At 08:21 PM 3/2/99 -0700, Brett Taylor wrote:
 
>What the hell do you need a response for?!  No one ASKED me to maintain
>the ports I maintain - I just do it.  It's pretty simple Brett.  Find
>yourself a piece of software that hasn't been ported.  Now make a port of
>it - inside the Makefile put:
>
>	MAINTAINER=   brett@lariat.org

In other words, just grab it? In the past, when I've asked to do such
things, TPTB have basically shooed me away.

>If you're talking about being a committer I can see why they didn't give
>you the commit privileges - 

I haven't even ASKED for commit privileges. I've asked to work on things
such as hardware compatibility, workarounds for rogue hardware, etc.
The people who were in charge of those and related areas considered me
to be trespassing on their turf and told me, perhaps not in so many
words, to go take a hike.

>> > It's not that it's hard to get it to do ELF _or_ a.out but to be able
>> > to do BOTH in one system.  Until you actually start trying to
>> > maintain some ports and do some work in this area, or let Satoshi
>> > explain to you in simple terms WHY it's hard then it's clear we're
>> > not going anywhere.
>
>> Then eliminate the need for that. Again, you're not "thinking outside
>> the box." 
>
>We DID eliminate the need to do both.  FreeBSD is now ELF - deal w/ it.  

Sorry, I'm running 2.2.8, which was released less than 90 days ago,
and it's not ELF. Deal with it.

>If you don't think 3.1 is stable then deal w/ the fact that new ports are
>not going to be available to you.  

Bzzzzt -- wrong answer. Not just for me, but for users in general. You
don't just drop support for a recently released product and try to
force an upgrade to a version that's only POSSIBLY the first stable one
in its branch. That's not only dumb, it's inconsiderate.

>If you think it's so easy to pull in FreeBSD ELF apps as is done for the
>Linux stuff then do it.  Back up all these "this should be done" comments
>w/ real action instead of talk and maybe then people would listen to you.

Again, in the past, when I've attempted to work on code that's someone's
"territory" I've been told to get lost. So, as I've now learned, the 
appropriate thing to do is to post a message that the person who maintains 
that code is likely to find and read. That's what I've done.

>> I think it requires a certain level of maturity to think in terms of
>> the users who want a stable, tested version rather than the bleeding
>> edge and accommodate them.
>
>The ports track STABLE.  3.* is the new STABLE branch.  

Too new to be considered for mission critical servers, I'm afraid.
Sorry, but I only ONCE made the mistake of jumping to a new version
too quickly. Never again. You can do that on your personal machine;
I can't do that on servers on which hundreds of users rely.

>Finally, it'd be nice if you showed some maturity and stopped whining
>about the GPL constantly.

Funny how the ignorant, the clueless, and the apathetic tend to brand 
others' concerns as "whines."

>I'm done w/ this as I might as well be talking to a fence post.

In other words, I might have a point, but rather than admit that you're
leaving. Fine.

--Brett Glass



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-advocacy" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19990302210310.009fccf0>