On 8/10/2011 2:45 AM, Ruben Van Boxem wrote:
> How does the buildbot work, *exactly*, when I ask it to do a
> mingw-x86-x86_64 build for example (for simplicity, assume I used the
> forcesrc page)? This would really help my understanding of it :)
Since I don't trust myself, let's go look at the
2011/8/10 Mook :
> On 8/8/2011 8:02 AM, Ruben Van Boxem wrote:
>> Dear mingw-w64 developers,
>
> First, welcome in your new packager hat! Except not quite, because
> you've been wearing a similar hat for a while already ;)
True, but this has a different goal of course (lots more platforms to
build
On 8/8/2011 8:02 AM, Ruben Van Boxem wrote:
> Dear mingw-w64 developers,
First, welcome in your new packager hat! Except not quite, because
you've been wearing a similar hat for a while already ;)
(I'm just going to ruthlessly snip all the bits I agree with, so please
read this as violently agr
On 8/9/2011 23:49, Jon wrote:
>> On Tue, Aug 9, 2011 at 10:44 AM, Jon wrote:
You guys rock, let that be clear ;-)
Kai and me have been discussing a proper release build setup for
mingw-w64. I would become the release packager dude that makes sure
proper releases are... rel
> On Tue, Aug 9, 2011 at 10:44 AM, Jon wrote:
> >> You guys rock, let that be clear ;-)
> >>
> >> Kai and me have been discussing a proper release build setup for
> >> mingw-w64. I would become the release packager dude that makes sure
> >> proper releases are... released.
> >>
> >> ...SNIP...
> >
On Tue, Aug 9, 2011 at 10:44 AM, Jon wrote:
>> You guys rock, let that be clear ;-)
>>
>> Kai and me have been discussing a proper release build setup for
>> mingw-w64. I would become the release packager dude that makes sure
>> proper releases are... released.
>>
>> ...SNIP...
>>
>> Any construct
On Mon, Aug 8, 2011 at 5:27 PM, Farkas Levente wrote:
>> --> binutils: latest trunk is the only sensible version
>
> does it means you always send all mingw/windows specific patches to
> binutils upstream and those are always merged? if not it'd be useful to
> keep all patches for the a given r
> You guys rock, let that be clear ;-)
>
> Kai and me have been discussing a proper release build setup for
> mingw-w64. I would become the release packager dude that makes sure
> proper releases are... released.
>
> ...SNIP...
>
> Any constructive thoughts are welcome, and help in getting the
>
2011/8/8 Farkas Levente :
> On 08/08/2011 05:02 PM, Ruben Van Boxem wrote:
>> - What we agreed on about versioning:
>> --> mingw-w64 should adopt a semi-rolling release model. It's
>> source only, so (Linux) packagers should just pick a (release) branch
>> and use its latest revision.
>
> it's
On 08/08/2011 05:02 PM, Ruben Van Boxem wrote:
> - What we agreed on about versioning:
>--> mingw-w64 should adopt a semi-rolling release model. It's
> source only, so (Linux) packagers should just pick a (release) branch
> and use its latest revision.
it's a support nightmare! how can one kn
> >> Yeah, a 7z .exe sfx thingie. If you have 7zip, you can open it as an
> >> archive, if not, you can double-click it and it will extract.
> >
> > Umm, I meant a real zip-sfx (self extracting zip which you can
> > actually run through unzip.) Howver, 7z should be acceptable
> > too.
> >
> > My
2011/8/8 Ozkan Sezer :
> On Mon, Aug 8, 2011 at 6:40 PM, JonY wrote:
>> On 8/8/2011 23:11, Ozkan Sezer wrote:
--> Sums up to 14 binary packages.
- Details:
--> I plan to build all prerequisites statically, prevents missing
dependencies on Linux etc... (which often do not h
On Mon, Aug 8, 2011 at 12:40 PM, Ozkan Sezer wrote:
>>
>> Yeah, a 7z .exe sfx thingie. If you have 7zip, you can open it as an
>> archive, if not, you can double-click it and it will extract.
>
> Umm, I meant a real zip-sfx (self extracting zip which you can
> actually run through unzip.) Howver,
On Mon, Aug 8, 2011 at 6:40 PM, JonY wrote:
> On 8/8/2011 23:11, Ozkan Sezer wrote:
>>> --> Sums up to 14 binary packages.
>>> - Details:
>>> --> I plan to build all prerequisites statically, prevents missing
>>> dependencies on Linux etc... (which often do not have tha latest
>>> cloog/ppl/g
On 8/8/2011 23:11, Ozkan Sezer wrote:
>> --> Sums up to 14 binary packages.
>> - Details:
>> --> I plan to build all prerequisites statically, prevents missing
>> dependencies on Linux etc... (which often do not have tha latest
>> cloog/ppl/gmp/mpfr/mpc)
>
> Only glibc then. What glibc versi
On Mon, Aug 8, 2011 at 6:31 PM, Ruben Van Boxem
wrote:
> 2011/8/8 Ozkan Sezer :
>> On Mon, Aug 8, 2011 at 6:02 PM, Ruben Van Boxem
>> wrote:
>>> Dear mingw-w64 developers,
>>>
>>> You guys rock, let that be clear ;-)
>>>
>>> Kai and me have been discussing a proper release build setup for
>>> min
2011/8/8 Ozkan Sezer :
> On Mon, Aug 8, 2011 at 6:02 PM, Ruben Van Boxem
> wrote:
>> Dear mingw-w64 developers,
>>
>> You guys rock, let that be clear ;-)
>>
>> Kai and me have been discussing a proper release build setup for
>> mingw-w64. I would become the release packager dude that makes sure
>
On Mon, Aug 8, 2011 at 6:02 PM, Ruben Van Boxem
wrote:
> Dear mingw-w64 developers,
>
> You guys rock, let that be clear ;-)
>
> Kai and me have been discussing a proper release build setup for
> mingw-w64. I would become the release packager dude that makes sure
> proper releases are... released.
Dear mingw-w64 developers,
You guys rock, let that be clear ;-)
Kai and me have been discussing a proper release build setup for
mingw-w64. I would become the release packager dude that makes sure
proper releases are... released.
I would like to make some things clear first:
- Linux binary rel
19 matches
Mail list logo
