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

Cannot install from release tar ball due to autogen #37

Open
morxa opened this issue May 18, 2017 · 5 comments
Open

Cannot install from release tar ball due to autogen #37

morxa opened this issue May 18, 2017 · 5 comments
Labels

Comments

@morxa
Copy link

morxa commented May 18, 2017

Installing from the release tarball fails because autogen.sh needs the git repository for version information.

To reproduce:

  1. Download the release tar ball

  2. Run ./autogen.sh in the extracted tar ball. This will fail with the following error:

     autogen.sh: error: Didn't find a git repository (or no tags found).  ``./autogen.sh`` uses git to create changelog and version information.
    

It would be nice if installing would work without cloning the complete repository.

I'm currently considering to package shyaml as a Fedora package. However, I cannot clone a repository while building a package, I need to be able to use the tarball. So while this might be a small issue for a normal user, it's a blocker for the Fedora package.

@vaab
Copy link
Member

vaab commented May 18, 2017

Yes, the default packages provided by github are not compatible with autogen.sh. I had the intention to invest time in providing real non-git source packages (and others). Would this help ?

@morxa
Copy link
Author

morxa commented May 18, 2017

Yes, that would work!

@vaab
Copy link
Member

vaab commented May 19, 2017

Ok, I have a somewhat tight schedule, I am not sure of how many time I have in front of a computer in the next days. I'd like to automate the github release process for all my projects in the same move, to ensure also a continuous and coherent flow of release.

@morxa
Copy link
Author

morxa commented Sep 27, 2017

It's been a while. What's the current status?

@vaab vaab added the pkg label Mar 6, 2018
@vaab
Copy link
Member

vaab commented Mar 6, 2018

Sorry, it won't be implemented for now, still under heavy load. But it is related it #27. I still want to do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants