From owner-freebsd-ports@FreeBSD.ORG Wed Nov 26 02:37:23 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0432916A4CE for ; Wed, 26 Nov 2003 02:37:23 -0800 (PST) Received: from lilith.bellavista.cz (lilith.bellavista.cz [213.235.167.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31C4143FBF for ; Wed, 26 Nov 2003 02:37:21 -0800 (PST) (envelope-from neuhauser@bellavista.cz) Received: from freepuppy.bellavista.cz (freepuppy.bellavista.cz [10.0.0.10]) by lilith.bellavista.cz (Postfix) with ESMTP id 070C832; Wed, 26 Nov 2003 11:37:15 +0100 (CET) Received: by freepuppy.bellavista.cz (Postfix, from userid 1001) id D0B6D2FDA03; Wed, 26 Nov 2003 11:37:14 +0100 (CET) Date: Wed, 26 Nov 2003 11:37:14 +0100 From: Roman Neuhauser To: freebsd-ports@freebsd.org, Allan Bowhill Message-ID: <20031126103714.GT340@freepuppy.bellavista.cz> Mail-Followup-To: freebsd-ports@freebsd.org, Allan Bowhill References: <20031027200046.33CF516A4DB@hub.freebsd.org> <20031027214510.GA52000@kosmos.mynet> <20031027223648.GC1004@zi025.glhnet.mhn.de> <20031028000708.GA52155@kosmos.mynet> <20031028004319.GF1004@zi025.glhnet.mhn.de> <20031125072702.GG340@freepuppy.bellavista.cz> <20031125064404.GA38625@kosmos.my.net> <20031125193010.GB67289@freepuppy.bellavista.cz> <20031125094426.GA39119@kosmos.my.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031125094426.GA39119@kosmos.my.net> User-Agent: Mutt/1.5.4i Subject: Re: Bug in ports howto question X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2003 10:37:23 -0000 # abowhill@blarg.net / 2003-11-25 01:44:26 -0800: > On 0, Roman Neuhauser wrote: strange date :) > Unfortunately, unlike other platforms, to send and receive mail on > FreeBSD, you need to a little about how mail works. I did not know a > lot in this area, before I started. Unfortunately? I don't agree with your assessment of the fact, but that's just me. > After learning a bit, I am left with the impression that internet > mechanisms and standards that support mail are complicated and > somewhat badly-designed. Evolutionary. (too many specialized > protocols, headers, acronyms) > > Despite all this, the configuration task is not that bad if you have > good instructions, but in principle, is overkill for submitting > ports. It's a little like trying to do square-foot gardening with a > combine. But if you have the time and documentation, you can get it > to work properly. Do you say port submission should be taken out using a separate mechanism? > :> This is a problem, becuase the PR was a new port. Now nobody will touch > :> the port becuase it looks too hard to deal with. So it will probably sit > :> in GNATS for 6 months, until someone takes it upon themselves to clean > :> it out. Then, I guess I can re-submit it. > : > : Just mail gnats-submit@ (or whatever's the correct address) with > : ports/#YOUR-PR-NR in subject and the correct patch attached. > > Yes. That's how I messed up the second submission out of three. Whatever > you do, don't send it as an attachment in outlook express :) Whatever you do, avoid Outlook [Express]. -- If you cc me or remove the list(s) completely I'll most likely ignore your message. see http://www.eyrie.org./~eagle/faqs/questions.html