Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: provide package files directly, not as zip files #271

Open
alterNERDtive opened this issue Nov 13, 2024 · 4 comments · May be fixed by #276
Open

Feature request: provide package files directly, not as zip files #271

alterNERDtive opened this issue Nov 13, 2024 · 4 comments · May be fixed by #276
Labels
enhancement New feature or request

Comments

@alterNERDtive
Copy link

I noticed that for the last couple releases the various distribution packages have come zipped up instead of the “naked” packages being attached to the release.

I’m assuming there is a reason for it, but running dnf install <url> is way more convenient than downloading an archive, unpacking it, and only then installing it :)

@GloriousEggroll
Copy link
Member

its because thats how github's workflows attach artifacts. we don't really have control/an easy solution for that without some heavy customization of artifact attachments, which is beyond my knowledge atm.

@alterNERDtive
Copy link
Author

You should be able to attach arbitrary files. As in, save it from the build workflow, then download in the release workflow.

Obviously I have no idea what you guys’ workflow is in general and if that’s feasible or if you have some other constraints.

@GloriousEggroll
Copy link
Member

You should be able to attach arbitrary files. As in, save it from the build workflow, then download in the release workflow.

Obviously I have no idea what you guys’ workflow is in general and if that’s feasible or if you have some other constraints.

I tried this once before and was not successful. Our workflow files are here:
https://github.com/Open-Wine-Components/umu-launcher/tree/main/.github/workflows

@R1kaB3rN
Copy link
Member

The constraint we're dealing with is specifically with Github's upload artifact workflow. See actions/upload-artifact#426.

I don't see this as a big problem, but if users want the "naked" resources, then they must use the Github API. However, if we want to change this and continue to have things automated, one way if is to automate the Github release and use the github-cli to upload the naked resource.

@R1kaB3rN R1kaB3rN added the enhancement New feature or request label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants