3.6 branch and release

John Marino dragonflybsd at marino.st
Sat Nov 9 04:23:40 PST 2013

On 11/9/2013 13:01, Dmitrij D. Czarkoff wrote:
> Hi!
> John Marino said:
>> In the case above, you would use "make dports-download", build git
>> from source, "rm -rf /usr/dports" then use "make dports-create" if you
>> want to convert /usr/dports to git repository.
> Wouldn't it save an extra step if "make dports-download" downloaded
> dports with .git snapshot, so that once git is built and configured, it
> could be instantly used for updating this tree instead of re-fetching
> it?

You are making several assumptions.
1. The person *wants* a git repo
2. The person wants a full repo instead of a shallow one
3. Conversely, the person wants a shallow repo instead of a full one
(somebody has to make a decision about repo typo in your proposal, 2 and
3 are mutually exclusive and somebody will always be upset at the choice)

make dports-download is much quicker than pulling from git.  If you
don't need git, or if this is a one-time use, you'd use this target.
The downside of pulling twice isn't that bad, even on slower connections.


More information about the Kernel mailing list