Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Jun 2012 13:10:47 +0100
From:      Kaya Saman <kayasaman@gmail.com>
To:        "Julian H. Stacey" <jhs@berklix.com>
Cc:        ports@freebsd.org, portmgr-feedback@freebsd.org
Subject:   Re: FreeBSD ports which are currently marked broken
Message-ID:  <CAPj0R5KXivo=d7RDPm7i%2BMuxUB8uh753k6LQDL45=Q6%2B222qmQ@mail.gmail.com>
In-Reply-To: <201206211201.q5LC1a5k099714@fire.js.berklix.net>
References:  <201206210828.q5L8SrdL078006@portsmonj.FreeBSD.org> <201206211201.q5LC1a5k099714@fire.js.berklix.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Is this only for "Ports" which don't build or "Ports" which have other issu=
es??

I posted an issue with the net/samba36 port where it doesn't seem to
create the PAM module??

Regards,


Kaya


On Thu, Jun 21, 2012 at 1:01 PM, Julian H. Stacey <jhs@berklix.com> wrote:
> 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 y=
et.
>
> Probably:
> =A0Many readers on ports@ often delete these periodic mails part unread, =
for
> =A0lack of time, as too verbose & hard to quickly scan (not read) through=
.
>
> =A0Remaining readers mostly just try to Quickly scan
> =A0Just the 2nd column in the top line of each section, ie
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0category/portname
> =A0Just to check ports they use are not mentioned,
> =A0trying to Not read irrelevant junk,
> =A0hoping to hit Delete ASAP.
> =A0 =A0 =A0 =A0If a port interest, they would be prepared to scan down
> =A0 =A0 =A0 =A0If not, delete ASAP, (as fewer are interested in creating
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0patches & filing send-pr for ports they do=
n'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:
> =A0 =A0 =A0 =A0echo $shorter_intro =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > posting
> =A0 =A0 =A0 =A0cat report | grep portname: | sed -e s/portname:// =A0 =A0=
 =A0>> posting
> =A0 =A0 =A0 =A0cat report =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0>> posting
> =A0 =A0 =A0 =A0cat footnotes_was_intro =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> posting
>
> Move the bulky introduction to foot notes. Consider the eye of a busy rea=
der:
> =A0"Argh! I got trapped reading that old boring blurb Again!
> =A0 Why no title like "Bad Ports Report" in top of body (not just Subject=
:)
> =A0 to prompt us if we've seen the title before we can skip the intro?
> =A0 Probably no ports that interest me anyway,
> =A0 Shall I wade through all that text, in case something of interest, Or
> =A0 Shall I gamble it's probably irrelevant to me, save time & hit Delete=
 ?"
>
> $shorter_intro=3D \
> =A0"Ports listed below have gone bad; Details below list; Notes below tha=
t."
>
> Cheers,
> Julian
> --
> Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix=
.com
> =A0Reply below not above, cumulative like a play script, & indent with ">=
 ".
> =A0Format: Plain text. Not HTML, multipart/alternative, base64, quoted-pr=
intable.
> =A0 =A0 =A0 =A0Mail from @yahoo dumped @berklix. =A0http://berklix.org/ya=
hoo/
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPj0R5KXivo=d7RDPm7i%2BMuxUB8uh753k6LQDL45=Q6%2B222qmQ>