On Tue, Feb 9, 2010 at 1:26 PM, <kmradke_at_rockwellcollins.com> wrote:
> justin.erenkrantz_at_gmail.com wrote on 02/09/2010 12:11:04 PM:
>> On Tue, Feb 9, 2010 at 8:05 AM, <kmradke_at_rockwellcollins.com> wrote:
>> > news <news_at_ger.gmane.org> wrote on 02/09/2010 01:02:52 AM:
>> >> 'getting subversion' still lists the 'tigris.org' windows binaries
>> >> that were provided by D.J. Heap.
>> >> But they are stuck at 1.6.6 and as D.J. stated in
>> >> http://subversion.tigris.org/ds/viewMessage.do?
>> >> dsForumId=462&dsMessageId=2423180
>> >> he won't build them any longer.
>> >> Shouldn't their be at least a note that states so?
>> > I thought someone else took them over. Ugh.
>> > What does the build process involve? I really need to
>> > keep the installer path the same, because moving to a
>> > different install path would be more painful at the moment.
>> If we need a windows "box" to do releases, I'm sure we can get a
>> Windows VM created on ASF hardware for our use. So, we shouldn't need
>> to depend upon any one individual to have a proper Windows config to
>> do build... -- justin
> That is what I was *hoping* could happen, but I do have a machine
> I could create a new VM on as well. I've built svn from
> source many times, but unfortunately not on Windows, so I'm definitely
> not going to be the fastest at spearheading this effort...
I suppose we could try to use ASF hardware to assist a volunteer that
wants to build Windows binaries, but AFAIK, the position of the
project has not changed about our desire to take any kind of ownership
of said binaries. Also, assuming that these binaries include things
like Neon, libintl and BDB I assume they still cannot be distributed
from ASF hardware and would have to be hosted elsewhere for download.
Received on 2010-02-09 19:38:42 CET