Concerning external package, I suggest that RIOT download and store
the archive in pkg folder then extract here in the right location to
be compiled. This is helpful when you work on a package so you don't
need to download it again every time after a `make clean` or when you
compile another example, you need to download it again.
What do you think?
So you mean that git-cache is already used and allow to download an
archive of a .git repo?
Could you give me an example of a package that is download as an
archive and store so you don't need to git clone again?
> I see! Very interesting feature and I really think it should be
> enabled by default! What's your opinion?
Not sure what you mean. The feature is enabled by default, the only thing you
need to do is to add git-cache to your $PATH.
That's not necessary. RIOT's build system looks explicitly in
`dist/tools/git` for `git-cache`. However, it is necessary to initialize
`git-cache` once with `$RIOT/dist/tools/git/git-cache init`. This will
create an empty bare git reposiroty in $HOME that is used to cache
the necessary git objects.
> I see! Very interesting feature and I really think it should be
> enabled by default! What's your opinion?
Not sure what you mean. The feature is enabled by default, the only thing you
need to do is to add git-cache to your $PATH.
That's not necessary. RIOT's build system looks explicitly in
`dist/tools/git` for `git-cache`. However, it is necessary to initialize
`git-cache` once with `$RIOT/dist/tools/git/git-cache init`. This will
create an empty bare git reposiroty in $HOME that is used to cache
the necessary git objects.
Yes it is what I mean, `git-cache` should be initialized automatically
at the first compilation. I do think it is possible and will avoid
people to forget to initialize it.