Github messages for voidlinux
 help / color / mirror / Atom feed
From: pudiva <pudiva@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: Aegisub-wangqr-git (fix #31637)
Date: Tue, 27 Jul 2021 05:11:31 +0200	[thread overview]
Message-ID: <20210727031131.GaHVlhQZJrfcOgXihf56deyduU0CRFrwkzv0krYZLwA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32162@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]

New review comment by pudiva on void-packages repository

https://github.com/void-linux/void-packages/pull/32162#discussion_r677085127

Comment:
> At worst, echo $version > somefile and patch cmake to read from that instead.

Unfortunately this is how **build/version.sh** generates a new **git_version.h** file:

```sh
new_version_h="\
#define BUILD_GIT_VERSION_NUMBER ${git_revision}
#define BUILD_GIT_VERSION_STRING \"${git_version_str}\"
#define TAGGED_RELEASE ${tagged_release}
#define INSTALLER_VERSION \"${installer_version}\"
#define RESOURCE_BASE_VERSION ${resource_version}"
```

I'm concerned with the `BUILD_GIT_VERSION_NUMBER` macro, that is set to `$git_revision`, that is defined as:

```sh
last_svn_revision=6962
last_svn_hash="16cd907fe7482cb54a7374cd28b8501f138116be"

git_revision=$(expr $last_svn_revision + $(git log --pretty=oneline $last_svn_hash..HEAD 2>/dev/null | wc -l))
```

which basically counts the number of commits since  `$last_svn_hash` and adds `$last_svn_revision`.

Now there are three options:

1. fetch with git
2. generate **git_version.h** on `pre_configure()`
   2.1. using hardcoded values manually extracted from git by the pkg maintainer (me???) on every update
   2.2. using the template's `$version` and never updating the other values

I did a little grepping but gave up following where the variable is ultimately used, so I'm not sure how important it is :woman_shrugging: 

To be honest, I'd rather go with what the maintainer supports, which is building from git, instead of creating more pkg maintenance overhead trying to build from the release tarballs that they'd have removed if they could:

> There are no release tarballs. “Source Code (zip)” and “Source Code (tar.gz)” listed on the release page are just automatically generated archives of the source, _without the `.git`-folder_ thus making them useless for regular building.Afaik GitHub doesn't allow to disable those.

https://github.com/wangqr/Aegisub/issues/116#issuecomment-886105613

... and I'm not even sure this is the only problem with the tarballs.

What do you think? :sparkles: :sparkles: :sparkles:

  parent reply	other threads:[~2021-07-27  3:11 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24  1:33 [PR PATCH] " pudiva
2021-07-24  1:44 ` abenson
2021-07-24  1:48 ` abenson
2021-07-24  1:49 ` abenson
2021-07-24  1:56 ` pudiva
2021-07-24  1:59 ` pudiva
2021-07-24  1:59 ` pudiva
2021-07-24  8:35 ` paper42
2021-07-24 12:56 ` pudiva
2021-07-24 13:18 ` [PR PATCH] [Updated] " pudiva
2021-07-24 13:21 ` pudiva
2021-07-24 14:22 ` paper42
2021-07-24 14:24 ` [PR REVIEW] " paper42
2021-07-24 21:15 ` ericonr
2021-07-24 21:19 ` [PR REVIEW] " ericonr
2021-07-27  3:11 ` pudiva [this message]
2021-07-27  3:40 ` ericonr
2021-07-29  0:18 ` pudiva
2021-07-29  0:45 ` [PR PATCH] [Updated] " pudiva
2021-07-29  0:48 ` pudiva
2021-07-29  0:50 ` [PR REVIEW] Aegisub: update to wangqr fork 3.3.2 " pudiva
2021-08-03 17:07 ` paper42
2021-08-03 17:07 ` paper42
2021-08-03 17:07 ` paper42
2021-08-03 17:07 ` paper42
2021-08-03 17:07 ` paper42
2021-08-03 20:11 ` pudiva
2021-08-03 20:12 ` [PR PATCH] [Updated] " pudiva
2021-08-03 20:12 ` [PR REVIEW] " ericonr
2021-08-03 20:13 ` ericonr
2021-08-03 20:14 ` [PR PATCH] [Updated] " pudiva
2021-08-03 20:14 ` [PR REVIEW] " pudiva
2021-08-03 20:15 ` [PR PATCH] [Updated] " pudiva
2021-08-03 20:15 ` [PR REVIEW] " pudiva
2021-08-03 20:17 ` [PR PATCH] [Updated] " pudiva
2021-08-03 20:19 ` pudiva
2021-08-03 20:20 ` [PR REVIEW] " pudiva
2021-08-04 12:01 ` ericonr
2021-08-04 20:27 ` [PR PATCH] [Updated] " pudiva
2021-08-10 21:56 ` pudiva
2021-08-10 22:13 ` pudiva
2021-08-11  2:13 ` [PR REVIEW] " ericonr
2021-08-11  2:13 ` ericonr
2021-08-11 12:06 ` pudiva
2021-08-11 12:07 ` pudiva
2021-08-11 12:12 ` [PR PATCH] [Updated] " pudiva
2021-08-11 12:13 ` [PR REVIEW] " pudiva
2021-08-11 12:13 ` pudiva
2021-08-11 12:22 ` pudiva
2021-08-11 12:23 ` pudiva
2021-08-11 12:33 ` pudiva
2021-08-11 15:09 ` ericonr
2021-08-12 10:11 ` pudiva
2021-08-12 17:56 ` [PR PATCH] [Updated] " pudiva
2021-08-12 18:17 ` pudiva
2021-08-13 14:50 ` pudiva
2021-08-13 15:51 ` pudiva
2021-08-13 17:59 ` pudiva
2021-08-13 18:02 ` pudiva
2021-08-23 17:54 ` pudiva
2021-08-27 16:05 ` [PR PATCH] [Updated] " pudiva
2021-08-27 16:08 ` pudiva
2021-09-10 17:16 ` pudiva
2021-09-16  2:28 ` [PR REVIEW] " ericonr
2021-09-16  2:56 ` ericonr
2021-09-16  3:20 ` ericonr
2021-09-16 22:38 ` [PR REVIEW] " pudiva
2021-09-16 22:42 ` pudiva
2021-09-17 13:18 ` [PR REVIEW] " ericonr
2021-09-17 13:18 ` ericonr
2021-09-17 18:12 ` [PR REVIEW] " pudiva
2021-09-17 18:45 ` ericonr
2021-09-17 19:10 ` [PR PATCH] [Updated] " pudiva
2021-09-17 19:11 ` pudiva
2021-09-17 19:15 ` pudiva
2021-09-20 19:37 ` [PR PATCH] [Updated] " ericonr
2021-09-20 19:38 ` ericonr
2021-09-20 19:38 ` [PR PATCH] [Merged]: " ericonr
2021-09-21  0:00 ` q66

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=20210727031131.GaHVlhQZJrfcOgXihf56deyduU0CRFrwkzv0krYZLwA@z \
    --to=pudiva@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).