Re: CVS commit: pkgsrc/mk/compiler

[Aleksej Saushev <asau%inbox.ru@localhost>]

Alistair Crooks <agc%pkgsrc.org@localhost> writes:

> On Sun, Dec 26, 2010 at 02:13:44PM +0000, Aleksej Saushev wrote:
>> Module Name: pkgsrc
>> Committed By:        asau
>> Date:                Sun Dec 26 14:13:44 UTC 2010
>> 
>> Modified Files:
>>      pkgsrc/mk/compiler: gcc.mk
>> 
>> Log Message:
>> Break with the past: use g95 as default Fortran compiler.
>> Welcome to the modern world of computing.
>> 
>> This is known to break DragonFly at least,
>> either port g95 or fix lang/gcc44 to work on NetBSD.
>> Unless there're packages that still think that Fortran is F77,
>> this shouldn't affect anything.
>
> I'm not too sure this was a good idea - certainly not just before a
> freeze for the pkgsrc-2010Q4 branch.  It also needs to get buy-in from
> the DragonflyBSD folks, too, and I did not see any of that.  If there
> was, please update the log message to that effect (i.e.  "discussed on
> users@ mailing list", or "approved by ...").

This change is prepared since summer, it was discussed and announced on 
tech-pkg.
20 days should be enough to come with objections.

It doesn't need anything, since it affects packages outside pkgsrc and
future packages. So far only one person called back and asked about this.
In that particular case, WIP developer was affected by language unknown
because of no support in stable branch. The rest of the world happily
lived not noticing anything.

I repeat again: all packages in pkgsrc use F77 and corresponding compiler(s),
they are not affected by this change, some packages may hardcode compiler,
they shouldn't be affected either, all packages that are really affected
are either not in pkgsrc or they have slipped away from my sight (I did
fix some packages that were introducing wrong dependency).

If package isn't broken, i.e. it doesn't list wrong dependency, it isn't 
affected.


-- 
HE CE3OH...