Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jan 2004 16:31:33 +0100
From:      Alexander Leidinger <Alexander@Leidinger.net>
To:        Nakata Maho <chat95@mbox.kyoto-inet.or.jp>
Cc:        ports-committers@FreeBSD.org
Subject:   Re: cvs commit: ports/lang Makefile ports/lang/ifc8 Makefile distinfo pkg-descr pkg-plist ports/lang/ifc8/files assert_fail.c cxa_atexit.c cxa_finalize.c errno_location.c exclude exclude_noportdocs ld.c linux_file.c linux_stat.c mcount.S ...
Message-ID:  <20040120163133.7b6ae4bd@Magellan.Leidinger.net>
In-Reply-To: <20040121.000530.719892310.chat95@mbox.kyoto-inet.or.jp>
References:  <200401191452.i0JEqDsi040194@repoman.freebsd.org> <20040119150116.GC28508@FreeBSD.org> <20040119165825.4aa630a8@Magellan.Leidinger.net> <20040121.000530.719892310.chat95@mbox.kyoto-inet.or.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 21 Jan 2004 00:05:30 +0900 (JST)
Nakata Maho <chat95@mbox.kyoto-inet.or.jp> wrote:

[CC trimmed]

> > I suggest to remove the port and let cvs@ do a repo copy of ifc to ifc7.
> No. I would like to wait for several months or so, since ifc8
> is still inmature state. higaki-san reported several defects of ifc8,
> and he don't want to recommend to use as a primary fortran compiler.
> Anyway, ifc8 is not very well tested, and ifc7 is quite tested.

The same applies to icc v8. That's the reason we have an icc7 port. It's
well tested and works and I don't want to get rid of it until icc v8 is
stable.

> so in the meantime, I don't think we need to do repo copy.

A repo copy is required regardless of the name (ifc8 or ifc7). The
reason I choosed icc7 instead of icc8 is: icc v8 will be mainstream
sometime in the future and icc v7 will not see much development from
this point in time. icc v7 can get removed then (no need to have a
versioned portname if there's only one version available). Now with the
ifc8 port, you don't have an associated cvs history anymore. And you
can't do a repo copy from ifc8 to ifc when ifc v8 is mature without
loosing the history of the actual ifc port.

It's up to you what name you want to use for ifc v8, but IMHO it would
be better to have an ifc7 and let ifc be v8.

If you want to keep the ifc8 name I still suggest to request a repo copy
(cvs has to do some repo surgery, removing icc8 completely and making a
copy from ifc to ifc8). After cvs@ finishes the work just commit your
actual version of the ifc8 port with an appropriate commit message over
the repo copy.

Bye,
Alexander.

-- 
           I will be available to get hired in April 2004.

http://www.Leidinger.net                       Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040120163133.7b6ae4bd>