all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: divoplade <d@divoplade.fr>
To: John Soo <jsoo1@asu.edu>
Cc: help-guix@gnu.org
Subject: Re: Newbie tries to add a snippet to an origin
Date: Sat, 01 Aug 2020 17:44:50 +0200	[thread overview]
Message-ID: <b8b4692278192c4c1856fbb02a9223a5eaaa4b62.camel@divoplade.fr> (raw)
In-Reply-To: <502B9149-6B35-46B4-8064-7631CB3E3AE0@asu.edu>

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 wish to use it to fix configure.ac. I can also
read the version number from a file in the repository (.tarball-
version), but it will not be part of a commit.

I have defined a guix template for two packages, "pomdappi" and
"pomdappi-dist", and I use the git repository and the gitlab CI
environment variables to fill in the blanks [2]. The "pomdappi-dist"
package creates the release tarball for "pomdappi", with the (dist-
package) constructor. The problem is that using a git source, I cannot
run "git describe"; so I need to patch the git source to add the
version number.

divoplade

[1] 
https://framagit.org/divoplade/pomdappi/-/tree/8-make-the-version-computation-reproducible
[2] 
https://framagit.org/divoplade/pomdappi/-/blob/8-make-the-version-computation-reproducible/dist



  reply	other threads:[~2020-08-01 15:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-01 15:17 Newbie tries to add a snippet to an origin divoplade
2020-08-01 15:26 ` John Soo
2020-08-01 15:44   ` divoplade [this message]
2020-08-01 15:50 ` Julien Lepiller
2020-08-01 16:00   ` John Soo
2020-08-01 16:23     ` divoplade
2020-08-01 16:27       ` John Soo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b8b4692278192c4c1856fbb02a9223a5eaaa4b62.camel@divoplade.fr \
    --to=d@divoplade.fr \
    --cc=help-guix@gnu.org \
    --cc=jsoo1@asu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.