From mboxrd@z Thu Jan 1 00:00:00 1970 From: myglc2 Subject: Re: Reorganizing guix package commands Date: Thu, 21 Apr 2016 08:34:26 -0400 Message-ID: <86y4875eel.fsf@gmail.com> References: <874mazi99k.fsf@gmail.com> <877ffual6i.fsf@gnu.org> <877ffujasf.fsf@gmail.com> <8737qh1tqm.fsf@gnu.org> <87a8ko7keg.fsf@gmail.com> <87shyg4npv.fsf@T420.taylan> <87lh48q7if.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58186) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1atDpS-0001Th-Fx for guix-devel@gnu.org; Thu, 21 Apr 2016 08:35:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1atDpO-00005V-AX for guix-devel@gnu.org; Thu, 21 Apr 2016 08:35:30 -0400 Received: from plane.gmane.org ([80.91.229.3]:38074) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1atDpO-00005P-4C for guix-devel@gnu.org; Thu, 21 Apr 2016 08:35:26 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1atDpG-0001S0-E9 for guix-devel@gnu.org; Thu, 21 Apr 2016 14:35:18 +0200 Received: from c-73-167-118-254.hsd1.ma.comcast.net ([73.167.118.254]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 21 Apr 2016 14:35:18 +0200 Received: from myglc2 by c-73-167-118-254.hsd1.ma.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 21 Apr 2016 14:35:18 +0200 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org ludo@gnu.org (Ludovic Courtès) writes: > taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis: > >> As an example of the pedagogic benefit of categorizing the commands: >> many users coming from other package managers are confused as to what >> exactly "installing" a package is in Guix. It actually consists of two >> steps, 1. to ensure the package is in the store (by building or >> downloading), and 2. adding it to the user's profile. But the term >> "install" doesn't reflect this, and makes users think in terms of >> traditional package managers where installing a package means putting >> its files into /usr. Introducing newcomers to a command like 'guix >> profile add' as the primary means of adding a package to their >> environment, and briefly explaining the "transparently makes sure the >> package is in the store" part, would have them immediately learn one of >> the basic working principles of Guix. > > Good point, I like it. :-) > > Ludo’. Yes, we should help newcomers delve into Guix. But a strangely named install instruction is not an effective way to accomplish this. We should find a better way. How about an animation of the processes you describe on the status line? Then a newcomer can learn while waiting for the software to install :-) The best way to make it easy for newcomers to see this animation is to give them what they expect -- an instruction named 'guix install'.