Date: Mon, 10 Aug 2020 10:21:21 -0400 From: Steve Wills <swills@FreeBSD.org> To: Lars Engels <lars.engels@0x20.net> Cc: "ports@FreeBSD.org" <ports@freebsd.org> Subject: Re: [HEADS UP] Planned deprecation of portsnap Message-ID: <87e338e4-d1bf-d26f-d60d-8ac55ae25b70@FreeBSD.org> In-Reply-To: <20200810132835.GN24022@e.0x20.net> References: <b920d0e6-72d3-b37c-e57e-6d027292e8db@FreeBSD.org> <20200810132835.GN24022@e.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On 8/10/20 9:28 AM, Lars Engels wrote: > On Tue, Aug 04, 2020 at 02:43:20PM -0400, Steve Wills wrote: > > I'm probably fine with this and I think that all of the (now) supported > methods have pros and cons. > To leverage the UX flaws of git and svn(lite) compared to portsnap > having a wrapper script around the two tools would be very appreciated. > > Something like > > # portsnap-ng --mode git --branch 2020Q2 --destination /ports/2020Q2 fetch extract > The package devel/git does not seem to be installed, do you want to install it? (Y/n) _ > > With sane defaults, so you can just run portsnap fetch extract like > you're used to and this > downloads the latest ports tree to /usr/ports using base svnlite(1). > > While we're here: Can we please have a separate user that is used to > checkout the tree? > > Lars > > > P.S.: Please DO NOT name the wrapper portsnap-ng. :-) > I think something like this will likely in many ways perpetuate many of the problems I listed in my original email, particularly with folks being on the wrong branch and not properly generating patches. Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87e338e4-d1bf-d26f-d60d-8ac55ae25b70>