If one runs an awk script on ports/INDEX, (eg awk -F\| '{print $2,$4}' INDEX | sed -e "s,/usr/ports/,," ) to show a boss, or customer etc that FreeBSD has lots of utilities that could help him, this entry: net/xgopher A brown, furry creature for burroring through Gopherspace. is non standard & not informative, for 2 reasons: the tool name `gopher' is not explicit the user may not know what gopher is or where to get it. Fix: patch enclosed ===== How-To-Repeat: As above
On Thu, 17 Oct 1996 jhs@freebsd.org wrote: [snip] > > net/xgopher A brown, furry creature for burroring through Gopherspace. > > is non standard & not informative, for 2 reasons: > the tool name `gopher' is not explicit > the user may not know what gopher is or where to get it. > > >How-To-Repeat: > As above > > >Fix: > patch enclosed > > ===== > *** old/ports/net/xgopher/pkg/COMMENT Thu Oct 17 14:55:16 1996 > --- new/ports/net/xgopher/pkg/COMMENT Thu Oct 17 14:57:32 1996 > *************** > *** 1 **** > ! A brown, furry creature for burroring through Gopherspace. > --- 1 ---- > ! An X-Windows front end for `gopher' (an internet fetching tool) Bah! But this is no better. It makes me rub my hands and think - so here we have a tool to fetch internets... It just isn't much of an improvement IMHO. Sander > ===== > >Audit-Trail: > >Unformatted: >
Hi, Reference: > From: Narvi <narvi@haldjas.folklore.ee> > Subject: Re: ports/1834: ports/net/xgopher/pkg/COMMENT patch > Date: Fri, 18 Oct 1996 20:03:54 +0300 (EET DST) > Message-id: <Pine.BSF.3.91.961018200104.22962A@haldjas.folklore.ee> > > > > On Thu, 17 Oct 1996 jhs@freebsd.org wrote: > > [snip] > > > > > net/xgopher A brown, furry creature for burroring through Gopherspa - ce. > > > > is non standard & not informative, for 2 reasons: > > the tool name `gopher' is not explicit > > the user may not know what gopher is or where to get it. > > > > >How-To-Repeat: > > As above > > > > >Fix: > > patch enclosed > > > > ===== > > *** old/ports/net/xgopher/pkg/COMMENT Thu Oct 17 14:55:16 1996 > > --- new/ports/net/xgopher/pkg/COMMENT Thu Oct 17 14:57:32 1996 > > *************** > > *** 1 **** > > ! A brown, furry creature for burroring through Gopherspace. > > --- 1 ---- > > ! An X-Windows front end for `gopher' (an internet fetching tool) > > Bah! But this is no better. It makes me rub my hands and think - so here > we have a tool to fetch internets... It just isn't much of an improvement > IMHO. > > Sander I first tried installing gopher & `man gopher` to get the original definition, but no luck, I agree mine's not great, If you can submit a better one line synopsis please do :-) Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/
Responsible Changed From-To: freebsd-ports->asami Satoshi is in charge of ports..
State Changed From-To: open->open
Responsible Changed From-To: asami->freebsd-ports Not my port.
Responsible Changed From-To: freebsd-ports->gpalmer It is Gary's port -- let him be the judge. .
>If one runs an awk script on ports/INDEX, >to show a boss, or customer etc that FreeBSD has lots of utilities that >could help him, this entry: > > net/xgopher A brown, furry creature for burroring through Gopherspace. [...] >! A brown, furry creature for burroring through Gopherspace. >! An X-Windows front end for `gopher' (an internet fetching tool) [...] > Bah! But this is no better. It makes me rub my hands and think - so here > we have a tool to fetch internets... It just isn't much of an improvement [...] > If you can submit a better one line synopsis please do :-) How hard can this possibly be? xgopher is a tool for navigating gopherspace. Does it have to be so complicated?
State Changed From-To: open->closed xgopher isn't part of the ports collection anymore, so this can be closed One less ;-)
>If one runs an awk script on ports/INDEX, > (eg awk -F\| '{print $2,$4}' INDEX | sed -e "s,/usr/ports/,," ) >to show a boss, or customer etc that FreeBSD has lots of utilities that >could help him, this entry: > > net/xgopher A brown, furry creature for burroring through Gopherspace. > >is non standard & not informative, for 2 reasons: This is a good example of how poor it is to leave these pr's sitting unnecessarily open for years and years. Now, _ONE YEAR_ less a month later, the pr still has not been closed despite being extremely simple to fix. It has cost developer time by cluttering the pr database, and probably caused submitter-frustration. After all of this, FreeBSD has still gained absolutely nothing since the xgopher port has been retired. Close the damn pr.