From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Blog: Guix packaging tutorial Date: Mon, 8 Oct 2018 21:59:39 +0200 Message-ID: <87in2cqkf9.fsf@elephly.net> References: <87in397jsd.fsf@ambrevar.xyz> <20180913191151.GA1865@jurong> <87woro5ocf.fsf@ambrevar.xyz> <20180914113302.elqrk3tvdkln2cde@thebird.nl> <87o9cmj0fc.fsf@ambrevar.xyz> <87mus6iypf.fsf@ambrevar.xyz> <87zhw02ea9.fsf@mdc-berlin.de> <87o9cex112.fsf@ambrevar.xyz> <87efdau5x2.fsf@gnu.org> <87murywuvn.fsf@ambrevar.xyz> <87lg7go8cv.fsf@gnu.org> <87va6kuyk4.fsf@ambrevar.xyz> <87sh1ot9m5.fsf@elephly.net> <87bm8bv4ao.fsf@ambrevar.xyz> <874le2j3ox.fsf@ambrevar.xyz> <87o9c4qxek.fsf@elephly.net> <87sh1g9t74.fsf@ambrevar.xyz> 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]:34442) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9bh2-0004uE-B9 for guix-devel@gnu.org; Mon, 08 Oct 2018 15:59:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g9bh1-0003gc-FD for guix-devel@gnu.org; Mon, 08 Oct 2018 15:59:52 -0400 In-Reply-To: <87sh1g9t74.fsf@ambrevar.xyz> 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: Pierre Neidhardt Cc: guix-devel , guix-blog@gnu.org Hi Pierre, > Ricardo Wurmus writes: >> * I wonder if maybe we should avoid using =E2=80=9Cguix package=E2=80=9D= for the first >> example and use =E2=80=9Cguix build=E2=80=9D instead. The reason is t= hat =E2=80=9Cguix >> package=E2=80=9D might cause additional builds to be performed depende= nt on >> the state of the user=E2=80=99s default profile (because of profile ho= oks). >> Using =E2=80=9Cguix build=E2=80=9D bypasses this issue completely. Wh= at do you think? > > Hmm... Installing a package is something more familiar than just "buildin= g". > Besides, with the new "cleaner" output, it's only a few lines which the u= ser is > going to see all the time, so I don't think there is much complexity we c= an > trim here. > > If we first build, then package, it makes the "easy" example an extra ste= p more > complicated. I assumed we would just build the package, not build and install. When packaging something, the common thing to do is to build, change, build again, =E2=80=A6 and in the end maybe install (or submit to the mailing lis= t). >> * =E2=80=9CCreate a folder=E2=80=9D =E2=80=93> =E2=80=9CCreate a directo= ry=E2=80=9D; =E2=80=9Cfolder=E2=80=9D is a GUI metaphor, >> but that=E2=80=99s nitpicking to be fair. I prefer =E2=80=9Cdirectory= =E2=80=9D, but use >> =E2=80=9Cfolder=E2=80=9D if you find it better :) > > Funny, I did not know that :p What is the GUI metaphor precisely? I pers= onally > prefer "folder" for the simple reason that it's shorter, but I don't mind > changing ;) A directory is a file system concept: a special kind of file that is a directory of files. IIRC the term =E2=80=9Cfolder=E2=80=9D was introduced = with Windows and the metaphor is that of a physical folder to store paper documents; it came together with the icon of a cardboard folder, which is still used in modern GUIs. >> * The section on =E2=80=9CRecursive importers=E2=80=9D does not mention = any recursive >> importers :) How about using the CRAN importer here, which supports >> recursive importing with the =E2=80=9C-r=E2=80=9D option? > > Hmm... I can't get this to work. > > --8<---------------cut here---------------start------------->8--- > guix import cran --recursive lubridate > --8<---------------cut here---------------end--------------->8--- > > returns only one package. That=E2=80=99s because the recursive importer won=E2=80=99t import packages= for which Guix already has package definitions (except for the very first). =E2=80=9Cr-lubridate=E2=80=9D already exists, and so do all its dependencie= s. Currently, =E2=80=9Cwalrus=E2=80=9D and some of its dependencies have not b= een packaged yet, so this command will give you representative output: guix import cran -r walrus > In fact, the "-r,--recursive" flag is missing from > the `guix import cran -h` documentation (while it's there for pipy). I c= annot > get it to work for pipy either. Oh, that=E2=80=99s a bug then. We should fix that. -- Ricardo