svn commit: r448034 - head/Mk

[Alexey Dokuchaev]

On Fri, Aug 18, 2017 at 03:45:23PM +0200, Mathieu Arnold wrote:
> Le 18/08/2017 ?? 15:03, Alexey Dokuchaev a ??crit :
> > On Wed, Aug 16, 2017 at 12:50:10PM +0000, Mathieu Arnold wrote:
> >> New Revision: 448034
> >> URL: https://svnweb.freebsd.org/changeset/ports/448034
> >>
> >> Log:
> >>   Add a git-clone target to clone the github repositories referenced in
> >>   ports using USE_GITHUB.
> > What is it useful for (specifically within the ports tree) that fetching
> > specific commit hash won't provide?  Cloning the repo implies that one's
> > intended to work on it and thus needs all the history.  For an arbitrary
> > port that one wants to build it's an overkill.  Also, how feasible is to
> > cache cloned repo (like we cache normal distfiles now)?
> 
> This is an easy way for the port maintainer to get the repository to
> check for newer versions, patches, or running git describe on a commit
> hash, or whatever they want to do with the repository, without having to
> look at the Makefile to see what the account and projects are, and type
> the git clone line.
> 
> It is not supposed to be used during the build process,

I see, thanks for explanation.

> and as such, I do not see why it would be needed to cache things.  Or
> how caching would work.

Exactly. :-)

./danfe