Date: Mon, 11 Jan 2021 15:17:55 +0100 From: Erwan David <erwan@rail.eu.org> To: freebsd-questions@freebsd.org Subject: Re: github ports Message-ID: <2c921d94-98dc-4916-6b1b-c3c2d2001932@rail.eu.org> In-Reply-To: <94ddb7c7d79c1614761fee4c28aaf367.squirrel@webmail.harte-lyne.ca> References: <mailman.98.1610366402.21235.freebsd-questions@freebsd.org> <94ddb7c7d79c1614761fee4c28aaf367.squirrel@webmail.harte-lyne.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 11/01/2021 à 14:54, James B. Byrne via freebsd-questions a écrit : > > > On Mon, January 11, 2021 03:42, Matthew Seaman wrote: >> On 10/01/2021 19:14, Valeri Galtsev wrote: >> >>> Just for my education: is there any advantage in using git like that instead >>> of portsnap? >> >> Just that the git method will be supported in the future, whereas >> portsnap is slated for removal, associated with the upcoming switch of >> ports from SVN to git due at the end of Q1 this year. >> > > A bigger advantage is that with git you get the complete development history. > Which means that if you need to rebuild an old package for a previous FreeBSD > release then you need only know the id of the last last commit made before the > packages were built for a specific release or quarterly update. With that > information one can checkout the entire code base as it existed at that moment > and rebuild from that. And with git these should be tagged so that you can > locate this point based on the release or quarterly build name or anything else > the maintainers consider significant milestones worthy of a tag.. > > But a big drawback is that as defauklt you get the whole history, which the moajority of us do not need and that some people cannot handle (not enough space, not enough bandwidth).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2c921d94-98dc-4916-6b1b-c3c2d2001932>