From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Store channel specification in profile Date: Mon, 06 Jan 2020 21:07:38 +0100 Message-ID: <874kx8gxh1.fsf@ambrevar.xyz> References: <87blsyelgm.fsf@ambrevar.xyz> <87tv69bezo.fsf@gnu.org> <87zhg1xvmo.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40198) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ioYfA-0006cX-7P for guix-devel@gnu.org; Mon, 06 Jan 2020 15:07:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ioYf8-0008Oe-K2 for guix-devel@gnu.org; Mon, 06 Jan 2020 15:07:43 -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 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable zimoun writes: >> > Like zimoun writes, it would be nice to have some sort of a =E2=80=9Cd= escribe=E2=80=9D >> > command for a regular profile. Actually maybe =E2=80=9Cguix describe = -p=E2=80=9D? >> > >> > Actually =E2=80=98guix describe -p ~/.guix-profile=E2=80=99 works but = doesn=E2=80=99t display >> > anything useful. We could fix that by recognizing the kind of profile, >> > somehow. >> >> Seems like a good idea. How do we define "anything useful" though? >> The provenance of packages? How would we format it? > > As I explained elsewhere, the file /manifest already > contains almost all the information we need (at least I think we need > ;-)). But its format is not complaint with the other format (channels, > manifest). And you answered: it is plumbing! :-) > My point is: this plumbing manifest file should be more > "format-friendly" -- still being plumbing -- and easily compliant with > the --channel or --manifest option, IMHO. I agree. But changing the format might break compatibility with existing functions that rely on it. In which places are manifests used? Should we not change the format, should we add a command line option to convert manifest to "manifest specifications" (those that work with `-manifest')? How do we include the provenance in manifest specifications? =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl4Tk4oACgkQm9z0l6S7 zH8xOAgAleaQDDR6Dw971bITOvCuiTzfoWlDF1ZqgNJQiBH+7i8B7CY+9ow0+duy zc+c54SeBfh/xUPA5WfDbLvAwV3GFAl7MIw9dWQ5J4MrpsXZmC61ADBWgVEdDndZ pjd+I2eWNt7sn7jEW44v76U1JUUGJuOKmNXUzRbN7orWrisiER0HA0QpUrrfx41w a82vwHqmUNz/JuNrv88YOWMbzb8W22kNjOMu7p43OgbFxci7dddz6J5lLAeJRjmP eKmo6R1v8TyI9o0/Vn1u7yi1W52ZjsbR+u4WCWzvVMOxwK34NS33U1gwDL/dbJqq xjfpQKd1kg5XtJQAsMdthEZfiewAwQ== =sJwZ -----END PGP SIGNATURE----- --=-=-=--