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:52:19 +0100 Message-ID: References: <87mudrxvs8.fsf@ambrevar.xyz> <87mudd59ho.fsf@gnu.org> <877e4glyc3.fsf@ambrevar.xyz> <87k18dvsqq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:41540) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iSiD0-0006tC-Um for guix-devel@gnu.org; Thu, 07 Nov 2019 08:52:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iSiCz-0006rA-M7 for guix-devel@gnu.org; Thu, 07 Nov 2019 08:52:22 -0500 In-Reply-To: <87k18dvsqq.fsf@gnu.org> 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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Guix Devel Hi Ludo, > I agree this is an important use case. It seems to me that the problem > here is being able to aggregate more than just packages. Yes, it's a bit more than that. We'd probably have to look at a couple of use cases to see what the most general content would be. > The Web application example above seems to be somewhere between a mere > and an full-blown . Perhaps we need an > intermediate abstraction that bundles together a profile along with some > lightweight services? > > Or, to put it differently, how do we define =E2=80=9Csuper-package=E2=80= =9D? That's the question. I don't pretend to have an answer, I just wanted to raise the question. There are use cases, such as Web servers, that move towards the service or even system abstraction. Other use cases would be just packages plus configuration, with no automatic execution implied. > =E2=80=98guix package --list-profiles=E2=80=99 was added to improve this = situation where > there=E2=80=99s no enforced convention. Unfortunately it makes no distinction between package profiles and channel profiles, so it's hard to use in scripts. > The question seems to be whether we should add more convention and less > configuration. Or have all configuration in a single file per user, with convenient defaults encoding a set of conventions. Trying to please everyone :-) Right now the only conventions I can think of are the two default profile names (~/.guix-profile for packages and ~/.config/guix/current for channels). And I wonder BTW if the latter is not an abuse of ~/.config, given that it contains a ton of software rather than just small configuration files, but that's a different question. > We should boil that discussion down to a list of things to implement. > :-) Definitely. But I'd like to start by compiling a list of use cases, to see how well they are served by what we have and then how they could be served better. Cheers, Konrad.