From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pjotr Prins Subject: Re: Using Guix archive (Help!) Date: Sun, 7 Jan 2018 10:16:24 +0100 Message-ID: <20180107091624.GA2981@thebird.nl> References: <20180103110836.GA15026@thebird.nl> <878tdb40kl.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53485) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eY77D-0007Lr-72 for guix-devel@gnu.org; Sun, 07 Jan 2018 04:19:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eY77A-0006pD-1q for guix-devel@gnu.org; Sun, 07 Jan 2018 04:19:39 -0500 Content-Disposition: inline In-Reply-To: <878tdb40kl.fsf@elephly.net> 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: Ricardo Wurmus Cc: guix-devel@gnu.org, "Frederick M. Muriithi" On Sat, Jan 06, 2018 at 01:46:18PM +0100, Ricardo Wurmus wrote: > I=E2=80=99m not sure, but it seems wrong. What I used to do is to crea= te a > profile and export that recursively: >=20 > guix archive --export --recursive \ > $(readlink -f /project/.guix-profile) | \ > gzip --stdout - > my-profile.nar.gz >=20 > This should include propagated inputs. I'll try that again, but it does not appear to be so elegant. Besides an archive is an archive ;). It should be a 'closure'. > > NAR files are signed. I think it would be very useful to be able to > > distribute unsigned NAR files. > > > > Q2: can signing/checking be made optional? >=20 >=20 >=20 > > I can't view the contents. > > > > Q3: how do we view the contents of a NAR file without unpacking it? >=20 > I don=E2=80=99t think you can. It=E2=80=99s a custom format implemente= d by > nix/libutil/archive.cc. Yes, we ought to do something about that. Nix nar files could be be unpacked before. I'll take a look at that. Not goot to have obscure formats. > > Q4: is there a nice way to include a profile path in the store that > > can be used quickly? >=20 > What do you mean by =E2=80=9Cinclude =E2=80=A6 in the store=E2=80=9D? = With the above command to > recursively export profiles you get a single archive that can be > imported to the store as a profile. It is elegant (if it works) and not elegant at the same time. I am thinking more of a symlink -S option like we have with pack. > > Q5: is there an elegant way to add those unpacked store items to th= e > > database? >=20 > What unpacked store items do you mean? I mean how to add the contents of a pack image to the store. What archive does, but then via the pack command. Well, if archive works properly, pack does not need to do anything ;) I know pack serves one purpose - deployment without guix - archive another - deployment with guix. It is that archive is not working so well, right now. pack could be supporting deployment on guix and archive could behave a bit more like pack. I'll take a look at the archive format. Pj.