Date: Mon, 20 Sep 2010 05:20:39 -0700 From: perryh@pluto.rain.com To: annulen@yandex.ru, jhell@dataix.net Cc: freebsd-ports@freebsd.org Subject: Re: Distributed Version Control for ports(7) ( was: Re: autoconf update ) Message-ID: <4c975197.1fY0dTyqrEwwwGi5%perryh@pluto.rain.com> In-Reply-To: <174981284967033@web24.yandex.ru> References: <4C91446F.3090202@bsdforen.de> <20100916171744.GA48415@hades.panopticon> <4C927ED0.5050307@bsdforen.de> <86zkvhfhaa.fsf@gmail.com> <4C92C14D.3010005@FreeBSD.org> <4C92F195.5000605@FreeBSD.org> <4C93A107.4070809@DataIX.net> <4c93f602.pzTXVEQ%2B3q2cRA23%perryh@pluto.rain.com> <4C94617B.3080702@bsdforen.de> <20100918141727.22a81b66@it.buh.tecnik93.com> <4C95AFE4.30608@DataIX.net> <174981284967033@web24.yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Konstantin Tokarev <annulen@yandex.ru> wrote: > Why not Git? One issue with either Git or Mercurial is that they are GPL. AFAIK FreeBSD prefers to avoid GPL in the base or in critical widely-used infrastructure if a viable non-GPL alternative exists. Granted SVN, currently used to manage src, is GPL; but its critical use is only on the project's own servers whereas the use being proposed for Git or Mercurial would involve their being used in a distributed manner (that being the whole point). A second issue with Mercurial is that it is written in Python, which seems to have adopted -- granted to a lesser extent -- the unfortunate Perl tendency for newer versions to be less than completely compatible with earlier versions. It would seem problematic if the Python version used by Mercurial were to be superseeded by an incompatible version, requiring the entire distributed user base to migrate.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4c975197.1fY0dTyqrEwwwGi5%perryh>