On Mon, Aug 10, 2020 at 3:21 PM Steve Wills <swi...@freebsd.org> wrote: > 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.
This seems to be an orthogonal issue. IMHO workflows to fix/update code which do not use a VCS are totally outdated. There should be no patches to fix things, but (git - if your VCS is git) branches. Then all these problems of "being on a wrong branch" are not there. Dima > > Steve > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
