镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

appveyor: include target architecture in Linux release asset names - #238

Open
drobilica wants to merge 1 commit into
OpenDriver2:masterfrom
drobilica:appveyor/linux-asset-arch
Open

drobilica wants to merge 1 commit into
OpenDriver2:masterfrom
drobilica:appveyor/linux-asset-arch

Conversation

@drobilica

Copy link
Copy Markdown

Why

The Linux builds target x86_64, as reflected by the *_x64 build configurations, but their release archive names (REDRIVER2_Release.tar.gz and REDRIVER2_Release_dev.tar.gz) don't identify either Linux or the architecture. Windows archive names identify their target as Win32.

I ran into this while adding REDRIVER2 to TarLink, my Linux manager for applications distributed as portable archives. TarLink uses release asset names to identify target platforms, so the current Linux names are ambiguous to it. I'm proposing the explicit name to make the target clear to TarLink and other downstream consumers, rather than adding a special case to my project.

What changes

Rename the Linux archives produced by .appveyor/AfterBuild.sh to include Linux_x86_64, for example:

  • REDRIVER2_Release.tar.gz → REDRIVER2_Linux_x86_64_Release.tar.gz
  • REDRIVER2_Release_dev.tar.gz → REDRIVER2_Linux_x86_64_Release_dev.tar.gz

This is a packaging-name change only. It does not alter the build or existing release assets. The AppVeyor artifact glob still matches the .tar.gz files.

Verification

  • bash -n .appveyor/AfterBuild.sh
  • git diff --check

An AppVeyor build will provide the end-to-end check of the produced artifact names. If this naming change doesn't fit the project's release conventions, please feel free to close the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant