-
Notifications
You must be signed in to change notification settings - Fork 21
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
Missing INSTALL, configure,... files #3
Comments
I wonder if it's possible to disable tarballs provision on GitHub, as they're not intended to be used by users at all. What you get from it is a copy of version-controlled git snapshot, where you're supposed to run The user-ready tarballs can be downloaded from linux.thai.net The reason is that we don't maintain auto-generated files in repository, as their contents vary with the autotools version you run. |
Meanwhile, I've added the link to official source release tarball in the release message: |
Thank you. I downloaded the tar ball and build from that. All went well.
Now that is clearer on how we should build the package. Would it be
possible to explain this in INSTALL, NEWS, changelog etc. files so we know
how to build the package. Let us say, we are promoting Thai Linux with
'easy to build' approaches. ;-)
sr
…On 22 December 2017 at 16:49, Theppitak Karoonboonyanan < ***@***.***> wrote:
Meanwhile, I've added the link to official source release tarball in the
release message:
https://github.com/tlwg/libthai/releases/tag/v0.1.27
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AM0pDCgSMEkqRlU2-6Qi2ZSk2zAgHPHOks5tC1EOgaJpZM4RKM3Y>
.
|
You can drag-n-drop the release tarball (with auto tools already run) in the edit window of a release. |
What I wish is the possibility to drag out the GitHub-provided zip file and tarball.
Done in the last release. |
Please supply these files so we can follow the usual ./configure, make... pattern.
The text was updated successfully, but these errors were encountered: