Date: Tue, 17 Jul 2012 15:35:05 -0400 From: Mike Meyer <mwm@mired.org> To: freebsd-hackers@freebsd.org Subject: Re: Pull in upstream before 9.1 code freeze? Message-ID: <20120717153505.42633535@bhuda.mired.org> In-Reply-To: <20120717183221.298430@gmx.com> References: <20120717183221.298430@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Jul 2012 14:32:19 -0400 "Dieter BSD" <dieterbsd@engineer.com> wrote: > >> Why not create a command wtf(1)? > > there are really lot of good features that can be made in FreeBSD. > > actually good, instead of that crap > While this is certainly not the most important improvement that could > be made (Fix the PRs!), the proposed wtf command could be useful. And it's been suggested a number of times on this thread. The proposed path is: 1) Write the WTF (or portsearch, or ...) command that can take a command name and return a list of suggested ports. Make it a port, since that's pretty much a zero-resistance move. 2) Add code to the port to use the *existing* hooks in some of the shells in ports (bash and zsh both have this, for instance) to invoke said command appropriately when they hit a command-not-found error. 3) Let people evaluate and play with that. 4) Now decide if we want this command in the base system. If the answer is mostly no, stop here. 5) Propose a patch to your favorite shell in the base system so the functionality added in step 2 will work in it as well. I'm not going to do this - this is the kind of thing that makes me loathe Linux. But if you want this functionality in your/the base system, your first step is clear - write the WTF program! Until that exists, the rest is just pointless debating. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120717153505.42633535>