optional disabling of the gitcache

Question

optional disabling of the gitcache

daniel-brosche opened this issue 6 years ago · 8 comments

I have an use case where the gitcache is not a good thing.
This article describes in which scenarios gitcache can be probelmatic (the point 2-3 are really a problem in one of my use cases).
Therefore I need an option to disable caching over an option.

What do you think?

Answer 1 · 2018-10-29T16:15:33.000Z

I think we could add a new environment variable (https://gitman.readthedocs.io/en/latest/setup/environment/) called GITMAN_CACHE_DISABLE. If set, repositories will be cloned directly.

Answer 2 · 2018-10-29T18:58:06.000Z

Ok, I will try that

Answer 3 · 2018-10-29T19:08:39.000Z

What are your typical development steps to verify your development stage locally. Actualy I currently install the development-stage globally by using the setup.py and then trying to debug (because in my mind gitman recursively calls gitman which needs to be system-wide installed). Is there a smarter way to do that?

Answer 4 · 2018-10-29T21:30:21.000Z

Check out how $ make demo is implemented. That will run the local version of gitman.

Answer 5 · 2018-10-30T08:13:16.000Z

Why is yorm listed in pipfile.lock and not in the pipfile itself?
Is this correct?

Answer 6 · 2018-10-31T15:22:04.000Z

Yeah, that's correct. The runtime dependencies are pulled in from setup.py.

Eventually I'll switch this project over to poetry, which make a lot more sense for libraries.

Answer 7 · 2018-10-31T21:48:49.000Z

Good to know. Poetry looks nice and clean...

Answer 8 · 2018-11-08T07:26:46.000Z

Next I will start to implement this small feature...