Re: Newbie tries to add a snippet to an origin

Hi divoplade, I’m glad you figured it out. I do want to say that most guix packages define the version number in the package definition. It would not be out of the ordinary to bump the version number in the scheme file. Good luck! John

Re: Newbie tries to add a snippet to an origin

Thank you so much for your help, now I can build both packages without hassle. The filled-in module template is dynamically computed [1], so I do not need to care about passing the version number around. https://framagit.org/divoplade/pomdappi/-/jobs/1068726/artifacts/raw/public/divoplade/packages

Re: Newbie tries to add a snippet to an origin

Hi divoplade and guix, Since you are using the gnu build system, I suggest making your version number a variable in the makefile. The good part of using a make variable is that you can use $(shell git describe ...) normally and override it when building with guix. You can use the make or config

Re: Newbie tries to add a snippet to an origin

I don't think this is how you are supposed to use snippet :). It's code executed from the root of the sources that changes it. Then guix repacks the modified sources and the result is the source for tge package. Look at the code in guix for more examples. Here's what I suggest: (source (origin

Re: Newbie tries to add a snippet to an origin

Hello, Le samedi 01 août 2020 à 08:26 -0700, John Soo a écrit : > What build system are you using? How do you use your version number? I am using the standard gnu build system with a git repository [1]. The version number is computed with "git describe --tags" (plus a little sed "s/^v//g"), and I

Re: Newbie tries to add a snippet to an origin

Hi divoplade, What build system are you using? How do you use your version number? Maybe there’s a simpler solution. - John

Newbie tries to add a snippet to an origin

Hello, I am trying to add a file named ".tarball-version" containing a fixed string at the root of my source. I tried several things, the most promising (I think) being this: (define-public pomdappi-dist (dist-package pomdappi (origin (method git-fetch) (uri (git-reference

Re: The sources with a git ref origin should also include the .git directory

Le samedi 01 août 2020 à 15:25 +0200, Ricardo Wurmus a écrit : > That’s on purpose, because the .git directory contains files that > prevent reproducibility. > Thank you, I will try something else then. divoplade

Re: The sources with a git ref origin should also include the .git directory

divoplade writes: > I am in the process of writing some code, and I like the fact that the > source of a guix package can have a git reference. However, when I use > it, the .git directory is not present when building the source. That’s on purpose, because the .git directory contains files tha

The sources with a git ref origin should also include the .git directory

Hello guix, I am in the process of writing some code, and I like the fact that the source of a guix package can have a git reference. However, when I use it, the .git directory is not present when building the source. Did I missed something? This is very inconvenient, because I use "git describe"

Re: what about custom licenses?

Hi, You can check guix/licenses.scm file. It contains how licenses are defined in Guix so you can build your own. There are projects with custom licenses there like wxwidgets. I hope this helps. Best, Ekaitz ‐‐‐ Original Message ‐‐‐ On Saturday, August 1, 2020 11:44 AM, Adam Kandur vi

what about custom licenses?

hi everyone! i packed some cl libs. but they have custom (foss) licenses. how i can describe it in guix?