Skip to content
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.

Does the package need to be a git repository? #68

Open
CMCDragonkai opened this issue Feb 22, 2018 · 3 comments
Open

Does the package need to be a git repository? #68

CMCDragonkai opened this issue Feb 22, 2018 · 3 comments

Comments

@CMCDragonkai
Copy link

The readme seems to imply that the code that you're packaging up needs to be a git repository? Can it be brought in otherways? I may have just a directory under src, and that is not a git repository.

@kamilchm
Copy link
Owner

It tries to find out what's the version of your package by looking for git history. So it should be git controlled at the moment.

@deliciouslytyped
Copy link

Is this what causes Error while creating repo for /build/src/some.domain/go/some-project: Unable to retrieve local repo information?

Though I'm a bit confused by that message because I'm pretty sure my package is a git repo, but I'm still debugging.

@deliciouslytyped
Copy link

deliciouslytyped commented May 8, 2019

Ok I'm trying to use go2nix save on a repository acquired via fetchgit and the .git looks kind of odd.

Edit: fetchgit results in some kind of strange .git. Also apparently there can be determinism issues if one keeps the .git, which makes sense because it could contain other branches and such. I solved the problem temporarily by just using normal git to get the repo I needed.

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

No branches or pull requests

3 participants