| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
- Detects if libgit2 is already fetched instead of constantly fetching. - Provides more meta information about libgit2 inside package.json.
|
About fetching libgit2: is it possible what fetched library has old uncompatible version? |
Sorry, something went wrong.
|
Yes, that is a good point. What would you suggest to handle this? Should I write out a tracking file named something like sha that contains the currently installed sha? That way we can compare and wipe out if it's outdated. |
Sorry, something went wrong.
|
Actually I could just write a file named identical to the sha and fs.stat that for testing. |
Sorry, something went wrong.
|
I think, will be enough to parse ./vendor/libgit2/include/git2/version.h |
Sorry, something went wrong.
|
Your solution will be simple |
Sorry, something went wrong.
|
If this looks good to you @3y3 can you merge? |
Sorry, something went wrong.
There was a problem hiding this comment.
Where is used pkg.libgit2.libgit2?
Sorry, something went wrong.
There was a problem hiding this comment.
Nowhere, must be remnant from something else. Good catch, removed.
Sorry, something went wrong.
|
Ok, I'm ready to merge it. |
Sorry, something went wrong.
|
@3y3 the checking is between python2 and python3 not python1. On systems like Arch Linux python defaults to 3 which doesn't work here. python2 is the aliased form. |
Sorry, something went wrong.
Better installation flow for developing.
|
Oh - now it's clearly. Merged. |
Sorry, something went wrong.
|
Awesome, thanks! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.