sdesc: "C, C++, Fortran compilers".
Isn't the short desc a bit, ehm, "short"?
I'd add the fact it does compile Java too, as an example, and that it is
the GNU Compiler Collection maybe.
BTW: can a shared version of libstdc++ be generated? I guess the answer
is "not yet" as it would be in the pac
Christopher Faylor wrote:
> On Tue, Jan 07, 2003 at 02:12:04PM -, Max Bowsher wrote:
>> I think that for maximum immediate gain, it is worth considering
>> this: Patch generic-build-script and mknetrel to detect certain files
>> (/usr/info/*.info and /etc/defaults/*) in a package, and add a
>>
On Tue, Jan 07, 2003 at 10:16:20AM +0100, Jan Nieuwenhuizen wrote:
>"John Morrison" <[EMAIL PROTECTED]> writes:
>
>> Christopher and I had a little conversation at the beginning of
>> December. It occured to me/us that a lot of cygwin packages
>> have postinstall scripts which just copy default ve
On Tue, Jan 07, 2003 at 02:12:04PM -, Max Bowsher wrote:
>I think that for maximum immediate gain, it is worth considering this:
>Patch generic-build-script and mknetrel to detect certain files
>(/usr/info/*.info and /etc/defaults/*) in a package, and add a postinstall
>script if found. Note th
>> Christopher Faylor wrote:
>>> That
>>> is basically asking 27 package maintainers to change the way they do
>>> things rather than just changing setup.exe.
No - the boilerplate Cygwin packaging script is quite popular.
Admittedly, I'd forgotten that mknetrel would need similar automagic.
> Ro
"John Morrison" <[EMAIL PROTECTED]> writes:
> Christopher and I had a little conversation at the beginning of
> December. It occured to me/us that a lot of cygwin packages
> have postinstall scripts which just copy default versions of
> configuration files into the correct location if they don't
