Date: Tue, 02 Oct 2012 13:37:26 -0500 From: Paul Schmehl <pschmehl_lists@tx.rr.com> To: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> Cc: FreeBSD Ports List <freebsd-ports@freebsd.org> Subject: Re: How to check out ports Message-ID: <17F1F6096650E45134B198CD@localhost> In-Reply-To: <44626syfjv.fsf@be-well.ilk.org> References: <6DE237A2D4133FBAED25FC26@localhost> <44626syfjv.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--On October 2, 2012 1:00:52 PM -0400 Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> wrote: > Paul Schmehl <pschmehl_lists@tx.rr.com> writes: > >> Are we supposed to be using cvs or svn to check out ports now? If >> cvs, I'm getting prompted for a password which fails. > > If you rarely need more than the latest version of the ports tree, then > portsnap(8) is worth strong consideration. If you have an existing setup > that's working (such as csup/cvsup/anonymous cvs), you can stick with > that until the svn-to-cvs export stops. Otherwise, use svn. > I obviously wasn't very clear. I'm a port maintainer. I need to update one of my ports. I used to do this by checking out the port into a purpose-created directory in which I would use cvs to make changes and test. After everything checked out, I would submit the diff. Now cvs isn't working, so how, as a port maintainer, do I check out a single port so I can update it and submit it in a PR? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17F1F6096650E45134B198CD>