[HEADS UP] Planned deprecation of portsnap

[Michael Gmelin]

On Fri, 7 Aug 2020 01:24:00 -0400
Steve Wills <swills at FreeBSD.org> wrote:

> Hi,
> 
> On 8/5/20 6:17 PM, Michael Gmelin wrote:
> > 
> > 
> > What will be the process to bootstrap git?
> >   
> 
> There are several options:

Thanks for your response - ideally there would be a lean default way
users can rely on (hence my question, I probably should've injected the
word "standard" in there).

> 
> 1. Install the git package provided by the FreeBSD project
In many cases this is the obvious choice, but in some scenarios not
possible.

> 2. Use svnlite to checkout a ports tree. (There will be git -> svn 
> replication.

Will this be a long-term option? I would very much like that - not for
development, I'm more than happy that I can *finally* use git there in
the future - but to have a chance to get and update a ports tree on
hosts (and inside of jails etc.) without installing git and all its
dependencies:

(typical dependency output from some older host)
git-2.27.0:
        p5-CGI-4.47
        expat-2.2.8
        p5-IO-Socket-SSL-2.068
        p5-Authen-SASL-2.16_1
        python37-3.7.7
        perl5-5.30.3
        p5-Error-0.17029
        curl-7.70.0_1
        pcre-8.44
        p5-subversion-1.14.0
        p5-Term-ReadKey-2.38_1
        gettext-runtime-0.20.2
        cvsps-2.1_2

This would also allow to write a simple/lean wrapper that can act as a
drop-in replacement for portsnap, as it doesn't require a special
bootstrap procedure and doesn't install any additional
packages/binaries on the system - therefore existing jail managers and
people's automation won't break.

> 3. Download a tar of the ports tree either from:
>      https://download.freebsd.org/ftp/ports/ports/
> 
> or cgit.

Would work too, but relatively expensive. Also, how often would it be
updated?

Thanks,
Michael

-- 
Michael Gmelin