From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: Re: Profiles/manifests-related command line interface enhancements Date: Thu, 07 Nov 2019 14:07:58 +0100 Message-ID: References: <87mudrxvs8.fsf@ambrevar.xyz> <87mudd59ho.fsf@gnu.org> <877e4glyc3.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:34994) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iShW5-0002vc-VG for guix-devel@gnu.org; Thu, 07 Nov 2019 08:08:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iShW4-0003Vb-Sz for guix-devel@gnu.org; Thu, 07 Nov 2019 08:08:01 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:59589) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iShW4-0003VN-IU for guix-devel@gnu.org; Thu, 07 Nov 2019 08:08:00 -0500 In-Reply-To: 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: zimoun Cc: Guix Devel Hi Simon, >> I can of course share a manifest file by putting it in a public >> repository. But that isn't necessarily the best way. > > From my opinion, it is not the problem of Guix. Guix should not force > a practise, as good it should be. The way the users share manifests is > the problem of users, not the Guix's one, IMHO. Guix should support good practices in my opinion. Sharing files that can contain arbitrary code (such as manifests) is not a good practice, for security reasons. For personal use, on the other hand, that flexibility is very valuable. > From my opinion, Docker tutorials seems really easy because 1. > everything is centralized and 2. they cheat (it is hard to replay a > random tuto couple of months later; from my experience.) I agree. I certainly don't want Guix to follow Docker in everything. We can always do better. > From what I understand, "guix time-machine" is the answer to this kind > of scenario. Right? Yes, in combination with "guix describe". > Personally, I do not like the "directory defined by convention and > referring to them by name" approach. The "package manager" Conda does > that and after some years using it (before switching to Guix \o/), > this approach appears to be also a mess. I never remembered the name That's valuable feedback. I have never used conda myself systematically, just a few times for following tutorials. > I prefer the Guix way and I store the profile (symbolic link) in the > project directory. This way, I always remember the name, I can quickly > create another one with a cryptic name -- naming is hard :-) -- and > weeks later I remember that it is attached to this project. That's how I work as well. But Pierre's recent document convinced me that profiles can also be a good way to modularize the global software collection of my account. It would indeed be nice to be able to update some parts (e.g. scientific software) more often than others (e.g. TeXLive). Cheers, Konrad.