From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?55m944GE54aK?= Subject: Re: Guix packaging tutorial with hand holding Date: Sun, 2 Jun 2019 00:20:48 +0200 (GMT+02:00) Message-ID: <570864249.1559426863378.eu.faircode.email@localhost> References: <443844029.1559193703837.eu.faircode.email@localhost> <8736kwl9bb.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 ([209.51.188.92]:46242) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hXCMx-0004aT-OW for help-guix@gnu.org; Sat, 01 Jun 2019 18:20:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hXCMw-0003ha-QZ for help-guix@gnu.org; Sat, 01 Jun 2019 18:20:55 -0400 Received: from minsky.hcoop.net ([104.248.1.95]:39074) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hXCMw-0003hH-NU for help-guix@gnu.org; Sat, 01 Jun 2019 18:20:54 -0400 In-Reply-To: <8736kwl9bb.fsf@elephly.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ricardo Wurmus Cc: help-guix@gnu.org Thu May 30 08:56:58 GMT+02:00 2019 Ricardo Wurmus : > You don=E2=80=99t need Github or any other externally hosted repository. = You > can use a local git directory just fine. So in the channel definition using a local directory what would the syntax = be instead of the =E2=80=9C(url=E2=80=A6=E2=80=9D bit? > > Second, working on the Guix git checkout is recommended as the best > > way. What is the way of working with Guix git checkout on a GuixSD > > system? I.e. should I pull, build it =E2=80=94 the git. Then what? Whe= re to > > run guix pull and guix package -u =E2=80=94 in the git, leave the SD v= ersions > > un-updated? > > When working with the Guix source code in a git checkout you don=E2=80= =99t > generally use =E2=80=9Cguix pull=E2=80=9D. Instead you use =E2=80=9C./pr= e-inst-env guix=E2=80=9D to > have Guix act on the modified source code. Using the git checkout is > how you can modify modules that are part of Guix, which is how you can > create patches that we can apply to Guix, so that everybody benefits > from your changes. > > If you want to keep using the git checkout as your primary installation > of Guix you can do that too, but combined with =E2=80=9Cguix pull=E2=80= =9D it=E2=80=99s a little > inconvenient. So what would the recommended workflow be, with a git checkout on top of Gu= ixSD? =E2=80=94 Only use =E2=80=9Cguix pull, guix package -u, and guix system rec= onfigure=E2=80=9D for GuixSD for root to have the base system up-to-date? =E2=80=94 Don't use =E2=80=9Cguix pull=E2=80=9D as regular user for GuixSD= , but install user packages from the git? =E2=80=94 In git use =E2=80=9C./configure --localstatedir=3D/var; make; ma= ke install=E2=80=9D? Also =E2=80=9Cmake install=E2=80=9D? =E2=80=94 Then to install packages use =E2=80=9C./pre-inst-env guix instal= l=E2=80=9D? -- Best regards / =E5=AE=9C=E3=81=97=E3=81=8F=E5=BE=A1=E9=A1=98=E3=81=84=E8= =87=B4=E3=81=97=E3=81=BE=E3=81=99 / S pozdravem / C =D1=83=D0=B2=D0=B0=D0= =B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC / Z powa=C5=BCaniem / Mit freundlichen Gr=C3=BC=C3=9Fen =E7=99=BD=E3=81=84=E7=86=8A