`guix package -u` upgrades packages to themselves

2018-04-11 Thread Pierre Neidhardt
I can run the following command as much as I want it will keep updating a bunch of packages to themselves. > guix package -u The following packages will be upgraded: guile2.2.3 → 2.2.3 /gnu/store/b90y3swxlx3vw2yyacs8cz59b8cbpbw5-guile-2.2.3 git:sen

Re: `guix package -u` upgrades packages to themselves

2018-04-11 Thread Ricardo Wurmus
Pierre Neidhardt writes: > I can run the following command as much as I want it will keep updating > a bunch of packages to themselves. That’s expected if you’ve upgraded Guix since installing the packages. (If you haven’t then it’s probably a bug.) That’s because the package version itself is

Re: `guix package -u` upgrades packages to themselves

2018-04-11 Thread Pierre Neidhardt
Sorry if I was confusing: the output remains the same after upgrade. I can repeat the command indefinitely, it keep "upgrading" the same set of packages as per the output (but it does not actually do anything). -- Pierre Neidhardt This restaurant was advertising breakfast any time. So I ordere

Re: `guix package -u` upgrades packages to themselves

2018-04-11 Thread Martin Castillo
On 11.04.2018 11:40, Pierre Neidhardt wrote: > > Sorry if I was confusing: the output remains the same after upgrade. > > I can repeat the command indefinitely, it keep "upgrading" the same set > of packages as per the output (but it does not actually do anything). > I see the same on 792ddfdc761

Re: How to install prerelease package versions (particularly Emacs)

2018-04-11 Thread Pierre Neidhardt
Mathieu Lirzin writes: > With the ‘#:recursive?’ keyword option set to #t, ‘local-file’ should > work for directories. Indeed, thanks for pointing out. I tried and it failed with starting phase `configure' source directory: "/tmp/guix-build-emacs-dev-26.0.91.drv-0/source" (re

Re: How to install prerelease package versions (particularly Emacs)

2018-04-11 Thread Pierre Neidhardt
Oleg Pykhalov writes: >>> In case of ‘emacs’ package recipe, ‘--with-source’ doesn't work for a >>> snapshot of the ‘master’ branch. >> >> Why? Because you’d need to run ‘autoreconf’ and the like? > > To run everything in ‘(arguments …)’ except ‘#:parallel-build? #t’. > > From http://lists.gnu.

Re: How to install prerelease package versions (particularly Emacs)

2018-04-11 Thread Pierre Neidhardt
Oleg Pykhalov writes: > Pierre Neidhardt writes: > >> I tried reusing your package snippet from >> http://lists.gnu.org/archive/html/help-guix/2017-09/msg00074.html by >> setting >> >>(url "git://localhost/~ambrevar/projects/emacs") > > I'm sorry for probably an obvious question

Re: Package request inxi

2018-04-11 Thread Pierre Neidhardt
I'm trying to package inxi. Does guix support optional dependencies? Or is it that I should just include them in the description? -- Pierre Neidhardt I think that's easier to read. Pardon me. Less difficult to read. -- Larry Wall in <199710120226.taa06...@wall.org> signature.a

Re: Package request inxi

2018-04-11 Thread Oleg Pykhalov
Hello Pierre, Pierre Neidhardt writes: > I'm trying to package inxi. Thank you for working on this! Let us know if you have more questions. > Does guix support optional dependencies? Unfortunately Guix doesn't. Instead you could use ‘(inputs …)’ and ‘(native-inputs …)’ which will not be ins

Re: Package request inxi

2018-04-11 Thread Pierre Neidhardt
Oleg Pykhalov writes: > Instead you could use ‘(inputs …)’ and ‘(native-inputs …)’ which will > not be installed to a user's profile but available in build phases. But those dependencies won't be used during the build phase: it's unnecessary load for the builder. -- Pierre Neidhardt He is a

Re: Package request inxi

2018-04-11 Thread Pierre Neidhardt
I'm running into a strange issue: Line 4506: $item =~ s/chipset|components|computing|computer|corporation|communications|electronics|electrical|electric|gmbh|group|incorporation|industrial|international|nee|revision|semiconductor|software|technologies|technology|ltd\.||\bltd\b|inc\.||\bi

Re: Package request inxi

2018-04-11 Thread Oleg Pykhalov
Pierre Neidhardt writes: > Oleg Pykhalov writes: > >> Instead you could use ‘(inputs …)’ and ‘(native-inputs …)’ which will >> not be installed to a user's profile but available in build phases. > > But those dependencies won't be used during the build phase Yes, unfortunately ‘inxi’ doens't pr

Re: Package request inxi

2018-04-11 Thread Oleg Pykhalov
Pierre Neidhardt writes: > I'm running into a strange issue: > Line 4506: > > $item =~ > s/chipset|components|computing|computer|corporation|communications|electronics|electrical|electric|gmbh|group|incorporation|industrial|international|nee|revision|semiconductor|software|technologies|tec

Re: Package request inxi

2018-04-11 Thread Pierre Neidhardt
Oleg Pykhalov writes: > Yes, unfortunately ‘inxi’ doens't provide like a ‘./configure’ thing to > discover and use inputs. But we could patch paths to input binaries. My point that the dependencies are not _needed_ during the build phase, so getting all the inputs induces extra load for nothin

Re: How to install prerelease package versions (particularly Emacs)

2018-04-11 Thread Pierre Neidhardt
For now I'll stick to Emacs 26 RC1. I've adapted the package declaration from "emacs" with the following changes: - Disable the scheme patch. - Disable tests. Find the declaration attached. -- Pierre Neidhardt When you get your PH.D. will you get able to work at BURGER KING? emacs.scm Descr