I'll throw this thought out here so it doesn't get lost: when it came
time for me to build a Windows release, I always used a quarantined Windows box
that had the minimum stuff installed and had never been on a network, to avoid
malware getting into the binaries.
The last thing I ever wanted to hear was some Windows user blaming FLAC because
a bad build infected him.? It was bad enough when some AV software was
misidentifying a release as infected; it took months after the virus defs were
updated for that stink to wear off.
>________________________________
> From: Erik de Castro Lopo <mle+la at mega-nerd.com>
>To: flac-dev at xiph.org
>Sent: Saturday, February 4, 2012 9:16 PM
>Subject: Re: [flac-dev] Meet the new maintainer
>
>Ralph Giles wrote:
>
>> On 4 February 2012 14:30, Erik de Castro Lopo <mle+la at
mega-nerd.com> wrote:
>>
>> > Is there any way to add say a windows machines with MSVC to that?
:-)
>>
>> There is. It's slightly complicated because (a) I don't have a
windows
>> machine with a public IP jenkins can ssh to, and (b) the jenkins box
>> itself doesn't have a public IP the java blob jenkins provides can
>> phone home to.
>>
>> I need to set up appropriate tunnels or packet forwarding.
>
>Would be very cool if you could set that up. Having Jenkins test
>on the platform that I do all of my hacking on is not all that
>useful. Having Jenkins test on Windows and OS X would be *really*
>useful.
>
>Erik
>--
>----------------------------------------------------------------------
>Erik de Castro Lopo
>http://www.mega-nerd.com/
>_______________________________________________
>flac-dev mailing list
>flac-dev at xiph.org
>http://lists.xiph.org/mailman/listinfo/flac-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.xiph.org/pipermail/flac-dev/attachments/20120425/cff2e240/attachment-0001.htm