Re: [Mingw-w64-public] [request] archive rubenvb builds without intermediate dir

[Jon <jon...@gm...>]

On Sat, Sep 24, 2011 at 4:47 PM, Ruben Van Boxem
<van...@gm...>wrote:

> 2011/9/23 Jon <jon...@gm...>
>
>> Currently the binary archives from mingw.org and the automated builds
>> from this project that I use put their artifacts in the top level of the
>> archive, while the rubenvb builds place their artifacts in an intermediate
>> 'mingw32' directory.
>>
>> This difference complicates some of my current automated build juju, and I
>> don't want to change my stuff :P
>>
>> Ruben...assuming this minimally tested patch works and doesn't break your
>> build process, can I cajole you into accepting and changing your future
>> releases?
>>
>
> I'm sorry, no. Frankly I find archives containing no single subdirectory
> (including the mingw-w64 autobuilds, but that's another story) very
> irritating, because when you "extract here" such an archive can mess up a
> complete non-related (in my workflow) mind. Lots of "official" packages do
> the same, even UNIX tarballs (just pick a random GNU source tarball).
>
> I do understand your issue, seeing that the autobuilds and mine differ in
> this respect. I copied sezero's behavior, which I obviously preferred.
>
> Ruben
>
>

Awww.  Ok, but playing with sharp pointy things is always so much more
interesting.

IIRC, the plan was for your builds to eventually replace the project's
current automated 32 and 64bit builds.  Is this (still) the idea, and if
yes, any gut feel on when you might do the switchover?

Jon