On Sat, Mar 31, 2012 at 10:50:31AM -0400, Nico Kadel-Garcia wrote:
> I'm spending way too much time backporting 1.6.17 work to RHEL 4, to
> publish for Repoforge. So far so good, I'm working from Mike Bauer work at
> plos.org, and tying it to my old Repoforge work for 1.6.x, and that's based
> on F
I'm spending way too much time backporting 1.6.17 work to RHEL 4, to
publish for Repoforge. So far so good, I'm working from Mike Bauer work at
plos.org, and tying it to my old Repoforge work for 1.6.x, and that's based
on Fedora 16 source RPM's on the last go-round. No big problem so far, it's
jus
Hi,
Are you sure you checked out the right directory from boost.
I performed a
$ svn co http://svn.boost.org/svn/boost/trunk boost
(as recommended on http://www.boost.org/users/download/#repository)
on my 2 year old notebook without solid state disk. (Just a simple 7200rpm
Ah so there was my misunderstanding on the question. The question was
regarding using the client to connect via a web server (i.e. dav svn
protocol) I was assuming a direct repo connection. i should read properly
before replying :)
rob
On Friday, 30 March 2012, Mark Phippard wrote:
> On Fri, Ma
