Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="US-ASCII"
MIME-Version: 1.0
Date: Sun, 15 Dec 2013 02:00:07 +0000
From: "David A. Holland" <dholland@netbsd.org>
Subject: CVS commit: pkgsrc/lang/ghc-bootstrap
To: pkgsrc-changes@NetBSD.org
Reply-To: dholland@netbsd.org
Message-Id: <20131215020007.B76AF96@cvs.netbsd.org>
Sender: pkgsrc-changes-owner@NetBSD.org
Precedence: bulk

Module Name:	pkgsrc
Committed By:	dholland
Date:		Sun Dec 15 02:00:07 UTC 2013

Added Files:
	pkgsrc/lang/ghc-bootstrap: DESCR Makefile PLIST distinfo
	pkgsrc/lang/ghc-bootstrap/patches: patch-ac patch-ad patch-aj patch-ak
	    patch-al patch-am patch-an patch-ao patch-ar patch-as
	    patch-mk_bootstrap.mk

Log Message:
Add a ghc-bootstrap package for making ghc binary bootstrap kits.
This is a ghc 6.8.3 package based on lang/ghc.

As of ghc 7.something, the old system of bootstrapping ghc from
generated C sources has been deprecated. While in theory we could move
pkgsrc up to that point using C bootstrap kits like the one currently
used by lang/ghc, there are several reasons not to: (1) it's a dead
end; (2) there is no available infrastructure for building such kits,
as in the past it was done by hand by the package maintainer; (3)
building ghc from C sources wasn't ever really fully supported anyway
and usually requires fiddling to make it work.

For this reason, by the power invested in me as one of the few people
who actually uses ghc for something nontrivial (much as I perhaps
regret doing so)... we will switch to binary bootstrap kits now.

The bootstrap kits generated here are just installable ghc packages
under a different name. This package depends on lang/ghc and uses the
installed ghc to build another copy; then that copy becomes the
bootstrap kit. That is, the bootstrap kit is the pkgsrc package you
get by doing 'make package' in this directory.

I have a (tested and working) patch to switch lang/ghc to use a new
bootstrap kit generated here, but I am intentionally holding off on
committing it until after 2013q4 is branched. That way anyone who
wants a bootstrap kit for a platform currently supported by lang/ghc
can get one by checking out 2013q4, building ghc, and then building
ghc-bootstrap.

Note that these bootstrap kits cannot be used with the wip/ghc
package; it uses a built but not installed ghc source tree as the
bootstrap kit. You can capture one of these from here if you really
want to by doing 'make' and then tarring up work/ghc-6.8.3... I think.
I haven't tested that, and for now it won't work anyway as wip/ghc is
too many versions ahead for such a build to be supported.

Because ghc can only be built with a recent ghc, updating lang/ghc to
a recent version will require a ping/pong process with ghc and
ghc-bootstrap. This is the chief reason to have a separate
ghc-bootstrap package; it should be perfectly possible to build
lang/ghc with a lang/ghc package as the bootstrap too.


To generate a diff of this commit:
cvs rdiff -u -r0 -r1.1 pkgsrc/lang/ghc-bootstrap/DESCR \
    pkgsrc/lang/ghc-bootstrap/Makefile pkgsrc/lang/ghc-bootstrap/PLIST \
    pkgsrc/lang/ghc-bootstrap/distinfo
cvs rdiff -u -r0 -r1.1 pkgsrc/lang/ghc-bootstrap/patches/patch-ac \
    pkgsrc/lang/ghc-bootstrap/patches/patch-ad \
    pkgsrc/lang/ghc-bootstrap/patches/patch-aj \
    pkgsrc/lang/ghc-bootstrap/patches/patch-ak \
    pkgsrc/lang/ghc-bootstrap/patches/patch-al \
    pkgsrc/lang/ghc-bootstrap/patches/patch-am \
    pkgsrc/lang/ghc-bootstrap/patches/patch-an \
    pkgsrc/lang/ghc-bootstrap/patches/patch-ao \
    pkgsrc/lang/ghc-bootstrap/patches/patch-ar \
    pkgsrc/lang/ghc-bootstrap/patches/patch-as \
    pkgsrc/lang/ghc-bootstrap/patches/patch-mk_bootstrap.mk

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.