From owner-freebsd-ports Mon Jan 8 6:36:30 2001 Delivered-To: freebsd-ports@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id D481637B6DC for ; Mon, 8 Jan 2001 06:32:52 -0800 (PST) Received: from bonsai.knology.net (user-24-214-88-8.knology.net [24.214.88.8]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id f08EWoo25290; Mon, 8 Jan 2001 08:32:50 -0600 (CST) Received: (from steve@localhost) by bonsai.knology.net (8.11.1/8.11.1) id f08EWnP11348; Mon, 8 Jan 2001 08:32:49 -0600 (CST) (envelope-from steve) Date: Mon, 8 Jan 2001 08:32:48 -0600 From: Steve Price To: Dag-Erling Smorgrav Cc: Ilya Martynov , freebsd-ports@FreeBSD.ORG Subject: Re: Is there any reason for FETCH_BEFORE_ARGS? Message-ID: <20010108083248.R86473@bonsai.knology.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Mon, Jan 08, 2001 at 02:12:11PM +0100 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 08, 2001 at 02:12:11PM +0100, Dag-Erling Smorgrav wrote: # # news/dnews does not use fetch(1), it sets FETCH_CMD to ftp(1) because # the master site's ftpd (some kind of BSDish ftpd running on RedHat # Linux) insists on anonymous logins using "anonymous", and libfetch # uses "ftp" (I can't remember why... "anonymous" is the standard # according to RFC1635). Apparently, Steve decided that reporting bugs # is for wimps, and committed "a serious hack" (his own words) rather # than bother to notify me of this problem. On the contrary, it never occurred to me at the time that the problem might be with fetch(1). Had I known or even imagined the problem was in libfetch, you can bet your house I would've assigned the problem report to you so that you could have fixed it the right way instead of complaining about what I did a month after I did it. # With a fixed libfetch, the port fetches fine without this hack. So commit it and undo my hack when the real fix has had time to make it into every version of FreeBSD that is supported by the Ports Collection. Meanwhile - right, wrong, or indifferent - with the changes I committed people can continue to use the port. My apologies for not having been nearly as thorough when dealing with this problem report as you have been months after the fact. I've spent the better part of the last month trying to recover from having worked 120+ hours a week for the last year at a company only to have all of my hopes and dreams squashed. These are stressful enough times for me without having you (DES) point a finger at me for not having done things your way. Fix it the right way and carry on. I'm back now and slowly catching up on all things FreeBSD. Please stick around and be my conscience DES, surely I'll make a more bad calls like this. I'll be the one addressing 100 PRs in a weekend and generally trying to contribute in my own way. You can be the one to sit back and complain about how I've done it. Deal? -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message