Packaging Coq

Does anyone know how to proceed? ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2014 Nikita Karetnikov ;;; ;;; This file is part of GNU Guix. ;;; ;;; GNU Guix is free software; you can redistribute it and/or modify it ;;; under the terms of the GNU General Public License

Re: Packaging Coq

> Should these arguments not be a double -- ?? No. pgpIWWS3Y1b3c.pgp Description: PGP signature

Re: Packaging Coq

Since people are commenting only on the recipe, I guess I need to clarify that I’d like to know why it fails to build. pgpVm4hxBpXvG.pgp Description: PGP signature

Re: Packaging Coq

I haven’t done the obvious thing… The package in Nixpkgs does more things, so I’ll try to change my recipe accordingly. pgp4000r6YKBh.pgp Description: PGP signature

FAQ

> Yes, but the Automake you installed by hand (in /usr/local I suppose?) > doesn’t look for .m4 files under /usr/share. Thus you need to: > export ACLOCAL PATH=/usr/share/aclocal I've seen similar questions several times. Maybe we should create a FAQ section in 'HACKING'. What do you think?

Re: FAQ

> It’s a good idea, probably as the first section in ‘HACKING’. Would you > like to propose a patch? Attached. Did I forget to mention anything? From 17a11ca78a4f71174edf57ec01f55934b1761363 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Tue, 9 Jul 2013 18:47:17 + Subject:

Re: Cross bootstrap!

(Please don't CC bug-g...@gnu.org if you decide to reply.) > It seems to be working on my machine. I've killed old processes and changed store-related permissions, it seems to work now (on master). pgpBaibNl35S6.pgp Description: PGP signature

Re: FAQ

> Looks good, but I would call it “Building from Git”, for instance, with > this particular error as a caveat. OK. > Remove “just”. OK. > I would also link to the “Installation” section of the manual, and to > “Installing Guix from Guix” in README. > WDYT? Can I use 'README' instead of 'HACKI

'core-updates': should we mention Graphviz in "Requirements"?

'make' fails with the following: [...] dot -Tpng -Tpng -Gratio=.9 -Gnodesep=.005 -Granksep=.5 -Nfontsize=9 -Nheight=.1 -Nwidth=.1 < "doc/images/bootstrap-graph.dot" > "doc/images/bootstrap-graph.png.tmp" /bin/bash: dot: command not found make[2]: *** [doc/images/bootstrap-graph.png] Error 1

Re: FAQ

> I’d say no, because that could lead “normal users” to think they need > Automake & co. to install Guix. OK, can I push this one? From cb6750a9869fc162d98eeb38ccb78e0846553f64 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Wed, 10 Jul 2013 06:13:59 + Subject: [PATCH

Re: FAQ

rmation. No, you are absolutely right. Do you have any other comments? From 64f56139dc2b3d92cf9b580414df609fdd951bf0 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Fri, 12 Jul 2013 20:31:28 + Subject: [PATCH] doc: Add "Building from Git" to 'HACKING'. --- HACKI

'patchelf' doesn't change shared libraries

make: *** [install] Error 2 Why does 'patchelf' fail to adjust shared libraries? (Note that '--set-interpreter' works fine.) ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2013 Nikita Karetnikov ;;; ;;; This file is part of GNU Guix. ;;; ;;; GNU Guix

Re: 'patchelf' doesn't change shared libraries

> Could you run ‘objdump -x .../ghc-pkg | grep PATH’, to check what its > actual RPATH/RUNPATH is? RUNPATH /nix/store/jndql2lmx3mzqmwhqh44bhm95wj8r9cy-gmp-5.1.2/lib:/nix/store/bz3az8a2699c77bgy8nm5cy77rypgw96-ncurses-5.9/lib $ objdump -x /nix/store/4g873aa2h6c8c2qfsiw0j1cbvhginx4

Re: Synchronizing descriptions with GSRC?

> That sounds fine then. I was probably being overly cautious. I share your concerns. Could you ask the FSF? I understand that they are very busy, but even a single mistake might spoil several years of work. pgpp2Y17makLK.pgp Description: PGP signature

Re: hydra.gnu.org back to life

> The non-responsiveness feedback in the substituter [0] had been > triggering a bug in our Hydra installation at http://hydra.gnu.org > whereby the server would enter an endless loop and effectively become > unreachable, to the point that hydra.gnu.org was hardly usable for > substitution. > Now

Re: hydra.gnu.org back to life

> The server is not responding right now. It's working again. Ludovic, did you restart it? pgpwYufZhg9Wv.pgp Description: PGP signature

'substitute*' fails with "string contains #\nul character" (was: 'patchelf' doesn't change shared libraries)

x --- Functional package management for GNU +;;; Copyright © 2013 Nikita Karetnikov +;;; +;;; This file is part of GNU Guix. +;;; +;;; GNU Guix is free software; you can redistribute it and/or modify it +;;; under the terms of the GNU General Public License as published by +;;; the Free Software

Re: Synchronizing descriptions with GSRC?

> Could you be more specific about what your concerns are? My main concern is that people say things like "I'm not sure, but let's do it anyway." Why don't you want to ask beforehand? > AFAIK most GNU web pages where we/I took summaries from at copyright > FSF, to start with. Yep, I forgot that

Re: 'substitute*' fails with "string contains #\nul character"

>> ice-9/boot-9.scm:106:20: string contains #\nul character: > Yes, that is expected. ‘substitute*’ is for textual files. > ‘fold-port-matches’ from (guix build utils) can be used for binary files > (see ‘remove-store-references’ for an example use.) Here’s what I’m trying to use: (use-modules

Re: patch for list-packages

> Btw, I can't see the patches as attachements, only inlined. Is > it a problem with my mail client or does everybody witness the same > behaviour ? I see the same. They also appear inline in the archives [1]. [1] https://lists.gnu.org/archive/html/guix-devel/2013-08/msg4.html pgp1UW2mnTqu

Re: 'substitute*' fails with "string contains #\nul character"

> For the purposes of bootstrapping GHC, I would rather steal whatever > trick Nixpkgs uses, though. :-) I can’t find anything relevant there. I suppose that Nix people don’t have to touch those binaries since they have ‘/bin/sh’ in a chroot. > ELF tools like Andy Wingo’s tools being added to G

Re: 'substitute*' fails with "string contains #\nul character"

>> I can’t find anything relevant there. I suppose that Nix people don’t >> have to touch those binaries since they have ‘/bin/sh’ in a chroot. > What string exactly are you trying to patch? Just /bin/sh? In which > binary? For now, at least ‘/bin/sh’ in ‘inplace/bin/ghc-cabal’. > I’m not sur

Re: 'substitute*' fails with "string contains #\nul character"

>> For now, at least ‘/bin/sh’ in ‘inplace/bin/ghc-cabal’. > What is it used for? Some kind of ‘system’ function? What do you mean by “’system’ function”? It’s used to build the libraries [1]. Here’s the source [2]. > If that is the case, perhaps you could replace the relevant calls to > that

Re: 'substitute*' fails with "string contains #\nul character"

>> Another possible solution is to ship our own bootstrap binary (like we >> do with Guile and Bash). But first, I’ll try to patch it. Are you OK >> with that? > With shipping a binary of GHC? Well, if that’s the only reasonable way > to do it, then yes. > GNU/MIT Scheme does that for instance

Re: Cross bootstrap!

> Can someone with a MIPS box test the Guile binary above? It works on my system, which uses a different ABI. pgp5r58AIws19.pgp Description: PGP signature

Re: Agreeing on some "rules" for packaging.

> At the GHM, a Fedora hacker (whose name I forgot) suggested that it > might be time for us to write down some "rules" as to how packaging > should be done. Do they have such rules? > For instance, Andreas suggested that patches should only be used if we > think they might be applied upstream, t

Re: Online hackathon ?

> Some people at the GHM seemed to be interested in packaging stuff in > Guix. Should we have a hackathon soon (1 or 2 weeks) where we could > help people on IRC for a whole week-end ? Do you think many people > might be interested ? I like the idea. I think there should be a low-hanging-fruit-li

Re: Goals for 0.4

> First, I’d like to release 0.4 by (or on) GNU’s 30th birthday, which is > on Sep. 28th [0]. On the 28th, I’d also like to have a bootable QEMU > image built with Guix, featuring at least the init system (dmd), a > console login, and bare utilities. That would be great. Because that’s the first

Re: Agreeing on some "rules" for packaging.

While we are at it, we could agree on quotation marks. I know that it sounds like bikeshedding… However, it doesn’t look right when some people use `' and others use ''. “Although GNU programs traditionally used 0x60 (‘`’) for opening and 0x27 (‘'’) for closing quotes, nowadays quotes ‘`like thi

Re: Goals for 0.4

>>> • New ‘--list-generations’ and ‘--delete-generations’ options for >>> ‘guix package’. I’ve been thinking about these options, and I’m not sure how they should work. Will it be enough to output a generation number and a list of packages when ‘--list-generations’ is used? For example: Gener

Re: Overlays

> So I think Guix nearly supports overlays, no? :-) What do NixOS people mean by “overlay”? Is it a remote collection of recipes? Does NixOS allow to use them without copying to the local storage (like ‘gnu/packages’)? I believe that the question was about these issues. If so, Guix doesn’t su

Re: [PATCH 0/2] Add tools for sysadmins: htop and dfc.

More nitpicking… > +(uri (string-append > + "mirror://sourceforge/htop/" > + version "/htop-" version ".tar.gz")) Could you place ‘string-append’ and "mirror://sourceforge/htop/" on the same line? > + (arguments '(#:tests? #f)) Why did you disable

Re: [PATCH 1/2] gnu: Add htop.

> + (synopsis "An interactive process viewer for Linux") > + (description > +"This is htop, an interactive process viewer for Linux. It is a > text-mode > +application (for console or X terminals) and requires ncurses.") I’d suggest to change “Linux” to “the Linux kernel” or “GNU/Linux”

Re: Agreeing on some "rules" for packaging.

> Yes, that change in the GCS is recent, and I haven’t completely changed > my habits. > IMO the rule should be: use Unicode quotation marks wherever possible > (almost everywhere), use what Texinfo prescribes in Texinfo (that is, > like `this' and ``that''), and use what the GCS says elsewhere.

Re: [PATCH 0/2] Add tools for sysadmins: htop and dfc.

> Yes. I never know what to do in such cases. Is there a document that > contains these coding-style rules, such as the PEP8 for Python ? The pretty-printing rule is described in SICP. Search for “There is no limit” [1]. However, that paragraph doesn’t say what to do when the line is too long.

Re: Goals for 0.4

> Rather, I would do: > --delete-generations=3..9 > It’s easier to parse and to type. > Likewise, it could even support: > --delete-generations=1month Here’s what I decided to use: --list-generations --list-generations=10 --list-generations=1,32,9 --list-generations=4..10 --list-generatio

Re: [PATCH 0/2] Add tools for sysadmins: htop and dfc.

> I think our messages crossed. What do you think of the “Coding Style” > section in ‘HACKING’? It’s OK. Let’s keep it. We could always augment it if there’s a need. pgpZMzPiDwgMP.pgp Description: PGP signature

Re: Git.

> + (synopsis "distributed version control system") Please capitalize the first letter of “distributed.” pgprlMyeoxis0.pgp Description: PGP signature

New ‘--list-generations’ and ‘--delete-generations’ options (was: Goals for 0.4)

I’m trying to handle the “last-month” and the “first-month” cases. I’d like to use ‘profile-numbers’* to construct an alist of generations and their creation dates. What can I use to get the creation date of a file? I can’t find anything in the manual. * We should rename it to ‘generation-numbe

MIPS64/N64 support (was: Goals for 0.4)

>> • MIPS64/N64 support: the bootstrap tarballs are now all available >> through cross-compilation from x86_64, so it’s “just” a matter of >> feeding them in bootstrap.scm and trying out. > I’m also interested in this one. Oh, I forgot that I’ll need five tarballs, not two [1]. Can I get the

Re: MIPS64/N64 support

> If you can cross-compile (really: substitute) them from x86_64, the > better (you can even log in to hydra.gnu.org and get them from there.) > Otherwise let me know and we’ll arrange something. $ ./pre-inst-env guix build binutils-static-stripped-tarball \ bootstrap-b

Re: [PATCH] gnu: Add itstool.

> + (uri (string-append "http://files.itstool.org/itstool/itstool-"; > + version ".tar.bz2")) The above should look like this: (uri (string-append "http://files.itstool.org/itstool/itstool-"; version ".tar.bz2")) > +each message to be translated

Re: New ‘--list-generations’ and ‘--delete-generations’ options

The attached procedure will be invoked when either option is called with an argument. It returns an empty list if the argument is not valid. Or when the needed generation can’t be found. Do you see any problems? Please check everything (especially the ‘first-month’ and ‘last-month’ functions).

Re: New ‘--list-generations’ and ‘--delete-generations’ options

> BTW, what did you think of the idea of using recutils format as the > output? (Either as the sole output format, or otherwise as a secondary > format.) I like the idea. It’s always better to use a documented format, especially when it comes with a mode for Emacs. And don’t forget that ‘--sear

Re: MIPS64/N64 support

> Oh indeed, using ‘-s’ was a good idea. Note that ‘guix build > bootstrap-tarballs’ is even faster to type. Thanks. >> Which Guile do I need? The stripped one, right? > The one that’s in the output of ‘guix build bootstrap-tarballs’ (I > forgot the name.) Yep, the stripped one. Can I downlo

‘--no-substitutes’ is ignored on i686 (was: Goals for 0.4)

> • Guix must be usable with the old Guile 2.0.5, since that’s what some > distros provide. At the GHM I realized that some people had weird > bugs with that Guile, notably in the substituter. I fixed a couple > of bugs, but there may be others around. > So, to 2.0.5 users: please run ‘m

Re: MIPS64/N64 support

>> Can I download the bootstrap tarballs from the web interface of Hydra? > Why not do ‘guix build bootstrap-tarballs -s x86_64-linux --target=...’? When I tested the previous set of binaries (see the mips64el branch), it was necessary to adjust ‘%url-base’ in ‘build-aux/download.scm’. It seems

Should ‘./configure’ fail when makeinfo is missing?

Should ‘./configure’ check for makeinfo? ‘make’ will fail when makeinfo isn’t installed. pgp6b8ytEaZGE.pgp Description: PGP signature

Re: Agreeing on some "rules" for packaging.

I’ve just fixed a small bug [1]. Maybe we should agree to run make distclean && ./boostrap && ./configure && make && make check before pushing, or will it be too tedious? Also, I don’t like the ‘license:’ prefix. What about something like ‘l:’? It’ll probably be even better to use ‘#:select’

Re: ‘--no-substitutes’ is ignored on i686

> In which command? guix build, guix package, guix-daemon? ‘guix build’ and ‘guix package’ when ‘guix-daemon’ runs without ‘--no-substitutes’. (I was able to reproduce this on a different i686 machine.) When the daemon uses the mentioned option, ‘guix build’ and ‘guix package’ work as expected.

Re: New ‘--list-generations’ and ‘--delete-generations’ options

> I’m asking because if we do that, ‘--list-generations’ may just as well > print out *all* the generation records. Users who want to select only > less than one-month old generations can do that with ‘recsel’, and we > don’t have anything more to do. > WDYT? I see recutils as an advanced option

Re: ‘--no-substitutes’ is ignored on i686

>> ‘guix build’ and ‘guix package’ when ‘guix-daemon’ runs without >> ‘--no-substitutes’. (I was able to reproduce this on a different i686 >> machine.) > What exactly makes you think it’s ignored? Could you copy/paste a > faulty-looking session? $ ./pre-inst-env guix build --no-substitutes gnu

Re: ‘--no-substitutes’ is ignored on i686

> I can confirm this bug on i686. The same happens with "guix package > --no-substitutes -i gnupg". On x86-64, everything works as expected. Does it mean that the daemon is the cause of the problem since the error is platform-specific? Also, note this line: The following derivations will be b

Re: MIPS64/N64 support

>> 3. Created ‘mips64el-linux-gnuabi64’ in ‘gnu/packages/bootstrap/’. > Hmm, I think we should just call it ‘mips64el-linux’ since the ABI is > really something orthogonal. I’ve already tried that: $ ./pre-inst-env guix build -K -s mips64el-linux-gnuabi64 hello […] ERROR: bootstrap binary not

Re: MIPS64/N64 support

>> I’ve already tried that: >> >> $ ./pre-inst-env guix build -K -s mips64el-linux-gnuabi64 hello >> >> […] >> >> ERROR: bootstrap binary not found "tar" "mips64el-linux-gnuabi64" > As I wrote, call it ‘mips64el-linux’, and put the binaries under the > directory of that name. I did that but forgo

Re: New ‘--list-generations’ and ‘--delete-generations’ options

> In that case, would you suggest --list-generations=rec to specify the > recutils output format (with no filtering)? No need for the ‘rec’ part. I propose to output all generations in the recutils format when ‘--list-generations’ is passed. > Age specifications would only be of the kind “at lea

Re: New ‘--list-generations’ and ‘--delete-generations’ options

>> How can I subtract 22 days from (current-time) using SRFI-19? > Note that the above example suggests that ‘string->duration’ returns a > time object with of type ‘time-duration’ (thus independent of the > current time.) Ah, OK. But we’ll have to subtract from (current-time) later anyway, righ

Re: New ‘--list-generations’ and ‘--delete-generations’ options

> By definition submatches 1 and 2 exist when RES is true. > Thus, I’d remove ‘safe-match:substring->number’ and do: > (match (string-match "^([0-9]+)\\.\\.([0-9]+)$" str) > (#f #f) > (matches > (let ((start (number->string (match:substring matches 1))) >(end (number->

[PATCH] guix package: Rename generation-related procedures.

Can I push this patch to ‘master’? From adb7b8383bd6748d12a0b782ab0f67b0b3e2995a Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Thu, 12 Sep 2013 17:31:53 + Subject: [PATCH] guix package: Rename generation-related procedures. * guix/scripts/package.scm (profile-numbers): Rename to

Re: New ‘--list-generations’ and ‘--delete-generations’ options

> I’d prefer clearer case analysis as shown above. OK, what do you think about this diff? If everything is fine, I’ll make it output generations in the recutils format. (Is it necessary to mention that ‘maybe-comma-separated-integers’ accepts something like ‘1,2,3,’ or ‘1,,,2’. Or should I chan

‘guix substitute-binary’ doesn’t have ‘--help’

Ludo (or anyone else), could you add ‘--help’? My version wouldn’t be helpful since I’m not familiar with that code. pgpYmgKsz1cUz.pgp Description: PGP signature

Re: New ‘--list-generations’ and ‘--delete-generations’ options

> Cool. The diff looks great... but it lacks tests. Yes, I wanted to finish the recutils part first. I’ve been thinking about that, and I don’t like that we’d have to use two record sets. It’d be necessary to post-process the output nearly every time. Then why bother? We can already filter t

Some thoughts on installers

I know it’s too early to talk about these issues. But I’m afraid that I’ll forget about them, and we’ll make the same mistakes as everyone else. I haven’t seen an installer that isn’t organized in a step-by-step fashion. A user is forced to press the “Next” button every 5 minutes or so. It’s im

PRELIMINARY: [PATCH] guix package: Add '--list-generations'.

XX). 3. ‘guix package -l -p test’ returns ‘guix package: error: test: extraneous argument’. (However, the same happens with ‘-I’.) 4. There must be a better way to write the test in ‘tests/guix-package.sh’. [1] https://lists.gnu.org/archive/html/guix-devel/2013-08/msg00173.html From 27e73d

Re: PRELIMINARY: [PATCH] guix package: Add '--list-generations'.

> I’ve just found a bug. On my machine, ‘guix package -p test -l 2d’ > and ‘guix package -p test -l’ should return the same set of > generations, but the fourth generation is shown twice in the former > case. Generations 4 and 5 have the same creation date for some reason: scheme@(guix ui)> date

[PATCH] guix package: Add '--list-generations'.

manual/texinfo/texinfo.html#index-table From 65a2d978e1b74cde953e81109dad33f2562e8294 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Thu, 19 Sep 2013 00:36:05 + Subject: [PATCH] guix package: Add '--list-generations'. * guix/scripts/package.scm: Import (srfi srfi-19). (generat

Re: [PATCH] guix package: Add '--list-generations'.

> That’s not necessarily a bug: it could be that generation 1 is just > slightly more than 48 hours old (the time should also be displayed, I > think.) Right, that’s what I was trying to show. Anyway, it shouldn’t be an issue now. OK, I added ‘~T’. > This should be present tense overall (for ex

package.scm: (profile-derivation (%store) '())

I’d like to know how ‘roll-back’ creates an empty generation because it’s necessary to do the same for ‘--delete-generations’. However, I fail to understand how (profile-derivation (%store) ‘()) works (or any other function that uses (%store)). I assume that some code should set ‘%store’ to somet

Re: package.scm: (profile-derivation (%store) '())

> ‘%store’ is a SRFI-39 parameter (info "(guile) Parameters"), aka. a > dynamically-scoped variable. > It is initialized with the ‘parameterize’ form, which sets its value for > the dynamic extent of its body. I don’t understand what code initializes ‘%store’. For example, I have one generation

[PATCH] guix package: Add '--delete-generations'.

00:00:00 2001 From: Nikita Karetnikov Date: Sun, 22 Sep 2013 18:50:06 + Subject: [PATCH] guix package: Add '--delete-generations'. * guix/scripts/package.scm (link-to-empty-environment) (switch-to-previous-generation): New functions. (roll-back): Replace internal functions wi

Re: Packages with libraries and binaries

> The two missing libraries are part of the package itself; apparently, they > do not get encoded into the rpath. Could this be handled somehow by the build > system? Should it be done in the package definition? Or should I set an > LD_LIBRARY_PATH? You can adjust RPATH with patchelf. Here’s an e

Re: Order of listed packages

> So I would suggest to revert the order of packages, listing them from > the first to the most recently installed. I agree. > The same applies probably to --list-generations. ‘--list-generations’ already does this. pgpwfmEUyqkO5.pgp Description: PGP signature

Re: Order of listed packages

>> The same applies probably to --list-generations. > ‘--list-generations’ already does this. Oh, I was talking about generations, so your argument is valid. I agree with this part as well, but let’s wait for other opinions. pgpo1ZfTAmQ7z.pgp Description: PGP signature

Generation 0 (was: [PATCH] guix package: Add '--delete-generations'.)

I think we should change ‘--list-generations’ to not output the zeroth generation. Even though it could be present in the profile, users shouldn’t be concerned about it. Currently, ‘--delete-generations’ ignores the zeroth generation. Other options seem even more confusing: 1. If you don’t have

Installing multiple packages at once

Someone on IRC said that they would prefer to write ‘-i foo bar baz’ instead of ‘-i foo -i bar -i baz’. Should we change this or allow both variants? And how hard would it be? pgpb1hJYB3Til.pgp Description: PGP signature

Re: [PATCH] guix package: Add '--delete-generations'.

> “Delete the generations matching @var{patterns} or ... when omitted.” > Or what actually? I would expect it to delete all the generations but > the current one when PATTERN is omitted, right? ‘--delete-generations’ deletes everything and points the profile to the zeroth generation. There are

Re: Generation 0

>> I think we should change ‘--list-generations’ to not output the zeroth >> generation. Even though it could be present in the profile, users >> shouldn’t be concerned about it. > Agreed. Good. > I think it should be impossible to remove Generation 0 through the > command-line tools, because t

FAIL: tests/guix-register.sh

HEAD (caf96debc257dee9ad8b0ea74cc6a8241c30dad4) fails. ‘guix-register.log’: + type -P sqlite3 /usr/local/bin/sqlite3 + echo 'select * from ValidPaths where path="/nix/store/z4pyj3rbgpqpd3mj0rxpbbpg45hlfcbh-guile-bootstrap-2.0";' + sqlite3 /home/tester/guix-test3/t-register-6453/nix/var/nix/db/db

Re: Generation 0

ion is always ignored? From 7fc042876bf00031d6b36b8d697984ce1ee1700e Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Mon, 23 Sep 2013 22:56:21 + Subject: [PATCH 1/3] tests: Test that '--list-generations' may not output anything. --- tests/guix-package.sh |3 +++ 1 file chang

[PATCH] guix package: Show which generation is the current one. (was: Generation 0)

other three.) From 7759ad3ad89d236e766639c0875540e60a503d16 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Tue, 24 Sep 2013 05:41:32 + Subject: [PATCH] guix package: Show which generation is the current one. * guix/scripts/package.scm (guix-package)[process-query]: Show that a gener

Re: [PATCH] guix package: Add '--delete-generations'.

I had noticed that ‘--roll-back’ doesn’t output anything with ‘--dry-run’, so I implemented ‘--delete-generations’ similarly. Maybe it would be better to print something. WDYT? >>> Agreed (in a separate patch.) I don’t think that I’ll have time for this before the release. I’d l

Re: [PATCH] guix package: Show which generation is the current one.

> Could we instead of a global (current-generation-number profile) > procedure? We’d store the number in a local variable here, to avoid > repeated ‘readlink’ calls. I don’t see how the former implies the latter. Could you expand on this? pgpo0JF9ism4T.pgp Description: PGP signature

Re: [PATCH] guix package: Add '--delete-generations'.

> Nothing has to be changed; it’s just that I’d prefer to put the bits > that introduce ‘link-to-empty-environment’ in a separate patch, for > clarity. > I could do it, but it may be easier for you to do it, no? Ah, I simply misunderstood. I’ll do it. pgpBmYpaLw3VH.pgp Description: PGP signatu

Re: GNU Guix hackathon on Sep. 28-29

> I will be physically present at the hackathon in Cambridge. Most Guix developers are not in the US, but it would be great if you could find interested people in Cambridge. > I have experience with Guile, but I haven't done much work with package > management systems before. That’s not a proble

Re: Generation 0

From f42056aa768a405a893b5846dad8f8fa576b1156 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Tue, 24 Sep 2013 22:11:16 + Subject: [PATCH 1/2] guix package: Exit with 1 when a generation cannot be listed. * guix/scripts/package.scm (guix-package)[process-query]: Exit with 1 when a generation

Re: [PATCH] guix package: Show which generation is the current one.

t to ‘master’? From 5ed5be5c786683cd5ec86d9834afca88d965d5f0 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Wed, 25 Sep 2013 01:55:27 + Subject: [PATCH] guix package: Show which generation is the current one. * guix/scripts/package.scm (guix-package)[process-query]: Show that a gener

Re: [PATCH] guix package: Add '--delete-generations'.

> Oh. I’d prefer if it would delete all generations but the current one. > That’s a fairly useful pattern: suppose you want to make space on your > disk (and you know you won’t need to roll back), it’d be handy to run: > guix package --delete-generations && guix gc > Whereas if you have to us

Re: FAIL: tests/guix-register.sh

> Could it be that something’s wrong with your setup? (Erroneous > LD_LIBRARY_PATH, etc.) Maybe. This test also fails on a different machine of mine. LD_LIBRARY_PATH is not set. pgpMTcknFjC6O.pgp Description: PGP signature

Re: Generation 0

>> What about these patches? Should the first patch also test the >> following case? >> >> +(let ((numbers (generation-numbers profile))) >> + (if (equal? numbers '(0)) >> + (exit 1) >> + (for-each list-generation numbers))

Re: FAIL: tests/guix-register.sh

> Are you using a distro-provide SQLite package, or something you built > yourself? > If the problem is widespread, we can just remove this test. No need. I solved the problem by installing SQLite from Guix. pgpwaGLweKqG9.pgp Description: PGP signature

Re: Generation 0

sh this patch? From 00188949e6c49592f6f2dc30bf21731ae142afc0 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Thu, 26 Sep 2013 02:00:06 + Subject: [PATCH 1/3] guix package: Exit with 0 when there is nothing to list. * guix/scripts/package.scm (guix-package)[process-query]: Exit with

Re: [PATCH] guix package: Add '--delete-generations'.

> Frankly, I don’t like it. I think the default behavior should not be to > let the user shoot themself in the foot. > WDYT? OK, what about these patches? Can I push them? From 86d29a8b233d5cf6549fbcddf43b185086b7d178 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Wed, 25 Se

Re: MIPS64/N64 support

s64el-linux-gnuabi64.tar.xz" diff --git a/gnu/packages/bootstrap.scm b/gnu/packages/bootstrap.scm index a1d4c7f..98d01d3 100644 --- a/gnu/packages/bootstrap.scm +++ b/gnu/packages/bootstrap.scm @@ -1,5 +1,6 @@ ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2012, 2013 Ludovic C

Re: Add Package Gl

Minor issues… >#:use-module ((guix licenses) > #:renamer (symbol-prefix-proc 'license:)) It’d better to use 'l: as a prefix to avoid (license license:something). You could also use #:select if it’s possible. >#:use-module (gnu packages fontutils)) > > Extra newline.

Re: MIPS64/N64 support

So I changed ‘bootstrap.scm’ and got the attached error message. Any ideas? diff --git a/gnu/packages/bootstrap.scm b/gnu/packages/bootstrap.scm index a1d4c7f..9151e01 100644 --- a/gnu/packages/bootstrap.scm +++ b/gnu/packages/bootstrap.scm @@ -63,12 +63,13 @@ (fetch store url hash-algo ha

Re: MIPS64/N64 support

So I ran this command: $ ./pre-inst-env guix build bootstrap-tarballs --target=mips64el-linux-gnuabi64 but it failed due to the already known problem: /tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.18.drv-0/build/libc_pic.a: could not read symbols: Archive has no index; run ranlib to add

Bootstrapping GHC

I’ve been thinking about GHC recently. (A quick reminder: there are binary versions [1], but we can’t use them because some binaries point to ‘/bin/sh’.) I believe the following should work for x86_64 and i686: 1. We fetch the source version [2] (manually), adjust ‘/bin/sh’, and build everyth

Re: MIPS64/N64 support

OK, I fetched the tarballs. Now I’m getting this error. $ ./pre-inst-env guix build -K hello [...] make-3.82/main.c make-3.82/README.OS2 make-3.82/remote-cstms.c phase `unpack' succeeded after 4 seconds shell-init: error retrieving current directory: getcwd: cannot access parent directories: I

Re: MIPS64/N64 support

> Could you try running the statically-linked bash from > ‘static-binaries.tar.xz’ and see if the same error occurs? Perhaps > strace it so we can see where that error comes from. I don’t see anything similar. > Looking at >

Re: Bootstrapping GHC

> I don’t know GHC, but apparently it can be bootstrapped from > intermediate generated C files: > http://www.haskell.org/ghc/docs/6.4.1/html/building/sec-porting-ghc.html > Wouldn’t that be better than fiddling with binaries out-of-band? The recent versions of the compiler don’t support this.

  1   2   3   >