Hi,

On Fri, Apr 09, 1999 at 11:28:52AM -0500, Glenn Johnson wrote:
> On Fri, Apr 09, 1999 at 03:52:58PM +0200, Jeremy Lea wrote:
> > I always thought the criteria for inclusion of things into the base
> > system was:
> > 
> > 1.  Needed for 'make world';
> > 2.  Needed to get a basic functioning server up and running;
> > 3.  Something usefull only within FreeBSD (like the kernel ;), or
> > 4.  Can't be effectively built outside of /usr/src.
> > 
> > If {g77|f77} can be built as a port, using the system EGCS, then to
> > port's it goes.  Otherwise why don't we include the Top 20 ports, or
> > maybe the Top 25, or...
> 
> First off, g77 is not your typical port. The build of g77 depends on
> having the source to gcc on your system. The last time I checked,
> installing the source was optional. The reason the current port of g77
> is marked broken is because of this.

See (4) above.  Adding it to /usr/src, with a NO_FORTRAN option, would
get my vote.

> Future: Now it may be true that newer versions of g77 may not build
> against whatever version of egcs we have but at least we would be
> guaranteed of having a functional Fortran compiler.

lang/g77-devel?  Depends on lang/egcs-devel?

> Many people don't seem to understand that FreeBSD can be used for
> workstations as well as servers and Fortran is *essential* on a
> scientific/engineering workstation. I don't doubt that there are more
> people using FreeBSD as a server but that doesn't mean that workstation
> users should be denied an essential tool because it takes up a few
> hundred kilobytes.

I'm a civil engineer, specialising in data analysis...

Regards,
 -Jeremy

-- 
  |   "I could be anything I wanted to, but one things true
--+--  Never gonna be as big as Jesus, never gonna hold the world in my hand
  |    Never gonna be as big as Jesus, never gonna build a promised land
  |    But that's, that's all right, OK with me..." -Audio Adrenaline


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Reply via email to