-
Notifications
You must be signed in to change notification settings - Fork 131
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
Please include nqp-configure in the release tarballs #699
Comments
@pstumpf Is this really about the submodule in the NQP source release files? (Which I suspect few people actually know about.) Or is this actually about the rakudo source release files? (The ones linked to on the http://rakudo.org/downloads website.) @Altai-man If I understand this ticket correctly it's basically a matter of adapting the release procedure. Isn't this ticket then better solved by you? |
@patrickbkr Yes, this is about the source releases generated from this (Raku/nqp) github repository. |
This issue is confusing me now. I just have checked out rakudo sources available via download on rakudo.org and found It currently looks like it's harder to find a source tarball without nqp-configure than with it included. @pstumpf could you, please, elaborate as to where do you download from? |
@vrurg I think the ticket is about "nqp-2021.04.tar.gz" we generate in this repo. |
@pstumpf Did you possibly download the archive labeled "Source Code (ext)"? Those are auto-generated by GitHub for every package and are best ignored. That's a plain bundle of the files of the respective tag. |
@Altai-man IIU vrurg correctly, those archives already contain nqp-configure. So the archives should already be fine. Question is: Can we do something about people downloading the auto-generated "Source Code" archives? Is it possible to add some descriptive text to the GitHub package? If yes we could add a short warning: "The |
Hmm, actually you are right, |
As the title says. As a downstream packager, this would make my work a lot easier.
The text was updated successfully, but these errors were encountered: