Date: Tue, 18 Sep 2012 22:27:56 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Eitan Adler <lists@eitanadler.com> Cc: Konstantin Belousov <kostikbel@gmail.com>, arch@FreeBSD.org, Doug Barton <dougb@FreeBSD.org> Subject: Re: Fallout from the CVS discussion Message-ID: <20120918202755.GB26107@ithaqua.etoilebsd.net> In-Reply-To: <CAF6rxgnGHtUVBP-Fh==b_2d5GWsNwCnMwqKFP951X_ZJGs_8iQ@mail.gmail.com> References: <CAF6rxg=qVUHe7tc9_AXgRdUtkoHOrixwNw-GsN7C7_r0FR990A@mail.gmail.com> <20120916053523.GJ37286@deviant.kiev.zoral.com.ua> <CAF6rxg=mm9OeVDX-dYC=FwnAZ-6pGjcRad=Gm9-mLx3QiPtqVQ@mail.gmail.com> <51B48339-D1FA-49CD-B582-1C58855B024E@bsdimp.com> <50563EA6.1050908@FreeBSD.org> <99E30CDE-AC9D-4615-8830-5EC511EE1BBB@bsdimp.com> <50578D98.7080902@FreeBSD.org> <3649BB84-30A9-4765-8BB6-2484B4B88343@bsdimp.com> <CAF6rxgnGHtUVBP-Fh==b_2d5GWsNwCnMwqKFP951X_ZJGs_8iQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 17, 2012 at 06:03:24PM -0400, Eitan Adler wrote: > On 17 September 2012 17:52, Warner Losh <imp@bsdimp.com> wrote: > [snip] >=20 > >>>> There is a compromise solution here that I have been hesitant to off= er > >>>> because I was really hoping that sanity would prevail. But why not > >>>> switch the default MK_CVS knob over to "no" now? That will give us an > >>>> opportunity to see if there really will be any fallout, and easily f= ix > >>>> it if there is. > >>> > >>> I believe that's already been done. > >> > >> It isn't now, but it sounds to me like you're saying that you're not > >> opposed to doing so? > > > > MK_CVS moving to 'no' by default is something we can do right away, sin= ce it is easy to figure out what went wrong for the people using cvs and pu= tting it back w/o needing to download anything new. Living behind firewall= s can make downloads a pita. I have had systems with very specific holes t= hat made it a PITA to download anything to them, and it is a common occurre= nce. > > > >> Eitan, if you're listening, I'd strike while the iron is hot. :) > > > > Since I thought that had already been done, please do so. Please make = sure that ObsoleteFiles does the right thing too :) Oh, and make sure UPDA= TING is updated. >=20 > I have some surrounding commits to get done first. I'd like to get > some of the existing documentation that refers to CVS removed or > modified first. > There is some consensus for making MK_CVS default to "no" early, so > I'll take that into account and commit that sooner than the above > listed conditions. > Does this change require a OSVERSION bump? I'm inclined to say yes as > the ports infrastructure might need to be aware of the change. >=20 What for? I don't see any reason why the ports tree would like to know about the cvs removal, do you have something in mind? regards, Bapt --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBY2UsACgkQ8kTtMUmk6EwvGgCdEdPhaVZ5X+yW4EJKD0VFrrRI tcUAoL+bYofy69f+fM+In5fQ/aQPFfoa =OzvE -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120918202755.GB26107>