Date: Wed, 4 Jul 2018 07:49:21 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Warner Losh <imp@bsdimp.com> Cc: "freebsd-arch@freebsd.org" <arch@freebsd.org>, Eitan Adler <lists@eitanadler.com>, Poul-Henning Kamp <phk@phk.freebsd.dk>, Bryan Drewery <bdrewery@freebsd.org> Subject: Re: xstr, mkstr Message-ID: <201807041449.w64EnMiI043329@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <CANCZdfpjpO8yb7_dty_fSe548BYwU5GRQgGimcFd8VKFLkyYHQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Wed, Jul 4, 2018 at 8:25 AM, Rodney W. Grimes < > freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > > > But, as I said early, lets just shelf all this "lets remove this or > > that cause of foo" until package base is done, and then a group of > > people should create a documented critiria list of what should or > > should not be in the base system, and do a tree wide sweep rather > > than have 100+ threads over the next 5 years about this or that. > > > > It does tie into the deprecation stuff too. Then shall this be tabled until that is finished please? > xstr, at least, needs major work to support modern C dialects. It's not > just old, it's also broken. A quick stroll through the code shows this. It > should go because it's not worth taking with us to pkg base. So add "Old", "Broken" to the list of critera and lets move on? Cost of taking this to pkg base should be 0, cost of this conversation is already >>> 0. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201807041449.w64EnMiI043329>