Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Nov 2017 19:49:11 -0800
From:      "Chris H" <bsd-lists@BSDforge.com>
To:        "Warner Losh" <imp@bsdimp.com>
Cc:        "freebsd-hackers@freebsd.org>" <freebsd-hackers@freebsd.org>, <lidl@freebsd.org>, "John Baldwin" <jhb@freebsd.org>
Subject:   Re: The future of fortune(6)
Message-ID:  <cd5d24bab0df89e2d23c34e172567ddd@udns.ultimatedns.net>
In-Reply-To: <CANCZdfp3OrC-GRUXvwCUb-gAW=d=EjTD2nihA31ME0rSwcgs4w@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 26 Nov 2017 10:16:49 -0700 "Warner Losh" <imp@bsdimp=2Ecom> said

> On Sun, Nov 26, 2017 at 10:11 AM, Warner Losh <imp@bsdimp=2Ecom> wrote:
>=20
> >
> >
> > On Thu, Nov 23, 2017 at 9:38 AM, John Baldwin <jhb@freebsd=2Eorg> wrote:
> >
> >> On Wednesday, November 22, 2017 03:01:17 PM Kurt Lidl wrote:
> >> > On 11/22/17 11:29 AM, Benno Rice wrote:
> >> > > I would like people=E2=80=99s opinion on which of the following tw=
o paths we
> >> should take:
> >> > >
> >> > > 1) Complete removal of fortune and freebsd-tips, remove its usage
> >> from the default =2Elogin/=2Eprofile files=2E
> >> > >
> >> > > 2) Reworking fortune(6) to remove the offensive fortune flag and m=
ake
> >> freebsd-tips the default, possibly by symlinking it as
> >> /usr/share/games/fortune/fortunes=2E
> >> >
> >> > Of these options, only #2 is approximately correct=2E
> >> >
> >> > I think just leaving the code as-is, and symlinking the freebsd-tips=
 to
> >> > be the default fortune datafile is the correct course of action=2E
> >> >
> >> > Removing the offensive flag handling dictates policy towards users
> >> > of the program=2E  If someone wants to add their own offensive datafil=
e
> >> > to their system, the code ought to allow them to select it=2E
> >>
> >> Agreed=2E  I think removing the default datfiles so that someone can
> >> maintain
> >> a port is fine, but we should leave freebsd-tips and the tool=2E  When
> >> the -o database was moved out of base we didn't remove the -o option, =
but
> >> instead extended the tool to work with string files in /usr/local=2E  Th=
e
> >> current state is fine=2E  The drama and lost time has always been about =
the
> >> 4BSD datfiles, never about freebsd-tips or the tool itself, so the iss=
ue
> >> is
> >> resolved=2E
> >>
> >
> > I like this plan=2E Let's call it consensus and implement=2E
> >
>=20
> [[ stupid gmail UI -- hit send too soon ]]
>=20
> I call it "consensus" but know there's a number of folks on one end of th=
e
> spectrum that want it gone completely, and some on the other end that wan=
t
> the datafile restored=2E And all sorts of opinions in between=2E Maybe "rough
> consensus" in that it's about the "centroid" of the mass of opinions on t=
he
> topic, and a good argument can be made=2E
>=20
> I find the "freebsd-tips is useful and makes the system more friendly,"
> argument persuasive=2E I think it would help our brand and user experience =
to
> have it there by default and it is very much the sort of thing that shoul=
d
> be in the base=2E Having the "fiunny" data files in a port and having the
> tool in the base system is a reasonable compromise, though one that will =
be
> revisited with pkg src in the future so if we get it wrong there's a
> natural decision point not too far away=2E
I like the way you proposed this, Warner=2E :)
While I'm still *firmly* in the "keep the original dataset camp"=2E I think
your proposal seems like the least abrasive, or easiest to swallow=2E :)
FWIW I think could probably live with this=2E

Thanks, Warner=2E

--Chris
>=20
> Warner





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cd5d24bab0df89e2d23c34e172567ddd>