From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 17 19:35:11 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C382106564A for ; Tue, 17 Jul 2012 19:35:11 +0000 (UTC) (envelope-from mwm@mired.org) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 418C98FC0C for ; Tue, 17 Jul 2012 19:35:11 +0000 (UTC) Received: by qcsg15 with SMTP id g15so635335qcs.13 for ; Tue, 17 Jul 2012 12:35:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:organization :x-mailer:face:mime-version:content-type:content-transfer-encoding :x-gm-message-state; bh=PUPSxmiG54u1t5QB1F5UIEAIzIvX9AtnRaMwArUkmUA=; b=SrLpG4KslDM7fPaDdYdKRl67wP1kC3z878wNdEnU7tdlHALyfB32OVueQTMt9MpqbL dwXurgMaEP8FqgrXUz3jj76KHwJZyk5IFomEUkgq+/7in+AkiHfKiDG27w+56lwWen+B zwINWYLxPLVoOttx+mdSwjGjywBsCv7uI4vB4GM2EgVrUeyRMlq0thf0gVACX+hYVgX1 YQrR+MH3a4ck13Y1q97X/GZ204HEj25VRH9BhAHKIt5keMe3baDBW0PMAB83F2CgeKB4 cXvWTC7ElAag40d+oFkvtlcM3m/HmUuRebTlb50u4mPxhpcf66vxDNQiZ/iFuc+r0sO7 tUFQ== Received: by 10.229.147.193 with SMTP id m1mr37927qcv.128.1342553710679; Tue, 17 Jul 2012 12:35:10 -0700 (PDT) Received: from bhuda.mired.org (74-140-201-117.dhcp.insightbb.com. [74.140.201.117]) by mx.google.com with ESMTPS id eb10sm27607777qab.4.2012.07.17.12.35.10 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 Jul 2012 12:35:10 -0700 (PDT) Date: Tue, 17 Jul 2012 15:35:05 -0400 From: Mike Meyer To: freebsd-hackers@freebsd.org Message-ID: <20120717153505.42633535@bhuda.mired.org> In-Reply-To: <20120717183221.298430@gmx.com> References: <20120717183221.298430@gmx.com> Organization: Meyer Consulting X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.3) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEXguIzRkGnhyaz069mXhW0WHRnbrnR9WCQ6LB0CchNMAAACSUlEQVQ4jV2TQW7jMAxFGaPQOgQEdZaGMsgBrAvUA03dCxj1Uu4U2gfwQD7AGNax51NK07RcxXz6/CSl0Ij450vkPG1jzpIZM1UwDCl/xB14TWnNX8A00Qj5a0mnVFVbVUz4MeErea2HikSRqZzY894zwg9p2+/AtO8LzxFED+tNAUFeU29iFOLRxlZAcdo9A8wi8ZBMV4BKPde82Oxrvs6BTkulQIClte0DLFzzsKk9j1MBex8iUaP00Bd78S/muyFScrTXz6zLkEUxJp+SabQfNOs4f4Jpx5qSZ/304PWwlEWP1cOn/mJQR7EOD+uKhjcBLziuL7xoY5Xm+VFAUSw/LwwwsHEHxihpwV4EJH0xXRkbw1PkRw+X4pEuSJwBggqk+HEYKkiL5/74/nQkogigzQsAFrakxZyfw3wMIEEZPv4AWMfxwqE5GNxGaERjmH+PG8AE0L4/w9g0lsp1raLYAN5azQa+AOoO9NwcpFkTrG2VKNMNEL5UKUUAw34tha0z7onUG0oBoNtczE04GwFE3wCHc0ChezAJ6A1WMV81AtY7wDAJSlXwV+4cwBvsOsrQMRawfQEBz0deEZ7WNpV2szckIKo5VpDHDSDvF1GItwqqAlG01Hh50BGtVhuUkjkasg/14bYFGCgWg1fSWHvmOoJck2xdp9ZvZBHzDVTzX23TkrOn7qe5U2COEw5D4Vx3qEQpFY2Z/3QFnJxzp7YCmSMG19nOUoe869zZfOQb5ywQuWu0yCn5+8gxZz+BE7vG3j4/wbf4D/sXN9Wug1s7AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQm2RBN3LlbZC4qPH5Y0Qte/1jRl73G74uZgYmK6mh08bZxgeTgCVmjbZCK+p+5efmWdKJia Subject: Re: Pull in upstream before 9.1 code freeze? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2012 19:35:11 -0000 On Tue, 17 Jul 2012 14:32:19 -0400 "Dieter BSD" 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. http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org