3 ms·

Surely a packager would be working off of the actual releases not a random git archive? And if they can’t wait for official releases, they’d be working off of

Surely a packager would be working off of the actual releases not a random git archive? And if they can’t wait for official releases, they’d be working off of the git repo?

Twirrim 3y ago
> Surely a packager would be working off of the actual releases not a random git archive? There are no official releases. To quote from the linked email: > No release tarballs or binaries are made available. Please do not use obsolete versions from older tarballs or zip files. Please remove any outdated links to these downloads -- they will cease to work soon. The only way to get a release version of LuaJIT is to compile it from the git repo.
- fullstop 3y ago
  > The only way to get a release version of LuaJIT is to compile it from the git repo. It will be interesting to see how this is packaged in, say, Ubuntu. Will they assign their own version numbers? Dates?
  - planede 3y ago
    I would say something along the lines of git-describe, and packages would need to depend on the exact version. If upstream can't commit to compatibility across release versions then I don't see it happening in distros either.
- layer8 3y ago
  Sounds like eternal beta.
  - andersa 3y ago
    It has been an eternal, abandoned beta for many years. But sounds like work resumed now. Maybe one day it shall be stable.
kzrdude 3y ago
The packagers can make their own snapshot, but they don't want to grab a full .git directory for the source - distributions such as Debian never want to do that: The packager is responsible for auditing all the code including copyright status in the artifacts - best not have the whole history of the project included in that case, because the task is then a little bit too big.
- fullstop 3y ago
  You can clone a specific tag or branch from a git repository without the full history. It looks like LuaJIT's git repository does not support this, although the github mirror does: # git clone -b v2.1.ROLLING --depth 1 git@github.com:LuaJIT/LuaJIT.git The git log looks like this: commit 2090842410e0ba6f81fad310a77bf5432488249a (grafted, HEAD, tag: v2.1.ROLLING) Author: Mike Pall <mike> Date: Mon Aug 21 03:18:35 2023 +0200 Merge branch 'master' into v2.1

Surely a packager would be working off of the actual releases not a random git archive? And if they can’t wait for official releases, they’d be working off of the git repo?

Twirrim 3y ago

> Surely a packager would be working off of the actual releases not a random git archive? There are no official releases. To quote from the linked email: > No release tarballs or binaries are made available. Please do not use obsolete versions from older tarballs or zip files. Please remove any outdated links to these downloads -- they will cease to work soon. The only way to get a release version of LuaJIT is to compile it from the git repo.

fullstop 3y ago
> The only way to get a release version of LuaJIT is to compile it from the git repo. It will be interesting to see how this is packaged in, say, Ubuntu. Will they assign their own version numbers? Dates?
- planede 3y ago
  I would say something along the lines of git-describe, and packages would need to depend on the exact version. If upstream can't commit to compatibility across release versions then I don't see it happening in distros either.
layer8 3y ago
Sounds like eternal beta.
- andersa 3y ago
  It has been an eternal, abandoned beta for many years. But sounds like work resumed now. Maybe one day it shall be stable.

kzrdude 3y ago

The packagers can make their own snapshot, but they don't want to grab a full .git directory for the source - distributions such as Debian never want to do that: The packager is responsible for auditing all the code including copyright status in the artifacts - best not have the whole history of the project included in that case, because the task is then a little bit too big.

fullstop 3y ago
You can clone a specific tag or branch from a git repository without the full history. It looks like LuaJIT's git repository does not support this, although the github mirror does: # git clone -b v2.1.ROLLING --depth 1 git@github.com:LuaJIT/LuaJIT.git The git log looks like this: commit 2090842410e0ba6f81fad310a77bf5432488249a (grafted, HEAD, tag: v2.1.ROLLING) Author: Mike Pall <mike> Date: Mon Aug 21 03:18:35 2023 +0200 Merge branch 'master' into v2.1