From owner-freebsd-ports@FreeBSD.ORG Thu Jun 21 12:01:57 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C3F71065673; Thu, 21 Jun 2012 12:01:57 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 8FFAD8FC1C; Thu, 21 Jun 2012 12:01:56 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBCF52.dip.t-dialin.net [93.203.207.82]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id q5LC1rdD040216; Thu, 21 Jun 2012 12:01:54 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id q5LC1g0R001986; Thu, 21 Jun 2012 14:01:42 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id q5LC1a5k099714; Thu, 21 Jun 2012 14:01:42 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201206211201.q5LC1a5k099714@fire.js.berklix.net> To: portmgr-feedback@freebsd.org From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Thu, 21 Jun 2012 08:28:53 GMT." <201206210828.q5L8SrdL078006@portsmonj.FreeBSD.org> Date: Thu, 21 Jun 2012 14:01:36 +0200 Sender: jhs@berklix.com Cc: ports@freebsd.org Subject: Re: FreeBSD ports which are currently marked broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 12:01:57 -0000 linimon@freebsd.org wrote: > As part of an ongoing effort to reduce the number of problems in > the FreeBSD ports system, we periodically notify users of ports Hi all, Reports should be ordered to draw the interest of readers, these aren't yet. Probably: Many readers on ports@ often delete these periodic mails part unread, for lack of time, as too verbose & hard to quickly scan (not read) through. Remaining readers mostly just try to Quickly scan Just the 2nd column in the top line of each section, ie category/portname Just to check ports they use are not mentioned, trying to Not read irrelevant junk, hoping to hit Delete ASAP. If a port interest, they would be prepared to scan down If not, delete ASAP, (as fewer are interested in creating patches & filing send-pr for ports they don't use). It's hard to quickly scan Just those 2nd col 1st line. To insert a simple initial list of nothing but port names: echo $shorter_intro > posting cat report | grep portname: | sed -e s/portname:// >> posting cat report >> posting cat footnotes_was_intro >> posting Move the bulky introduction to foot notes. Consider the eye of a busy reader: "Argh! I got trapped reading that old boring blurb Again! Why no title like "Bad Ports Report" in top of body (not just Subject:) to prompt us if we've seen the title before we can skip the intro? Probably no ports that interest me anyway, Shall I wade through all that text, in case something of interest, Or Shall I gamble it's probably irrelevant to me, save time & hit Delete ?" $shorter_intro= \ "Ports listed below have gone bad; Details below list; Notes below that." Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/