At long last: 2014.2.0.0 Release Candidate 1

Mark Lentczner mark.lentczner at gmail.com
Fri Jul 25 14:18:37 UTC 2014


On Fri, Jul 25, 2014 at 12:32 AM, Sven Panne <svenpanne at gmail.com> wrote:

> The structure on GitHub is a bit confusing

As with past releases, we generally work on a branch until release.


> With 2013.2.0.0 one could
>
easily specify a --prefix in the configure step, and everything worked
> as expected.

I didn't realize anyone used it. But it should be easy enough to add.

What about packages being unregistered?

It is intentional. The package registrations are all prepared, but the
final registration should happen after the tree is moved into place.
Conventionally this was part of "make install". For the build, there should
be an "activation" script added to the tree that the user runs after
copying the tree to the final system.


> Even keeping the
> distinction between the GHC parts and the rest of the platform is not
> useful from a user perspective and to large parts totally artificial:
> Why e.g. is haddock below GHC part, but alex below the HP part?

Becuase the platform is built from the GHC bindist, and traditionally we've
keep the GHC supplied portions "pristine".


> Partly, yes. It doesn't matter in detail how things happen, but we
> need the ability of the simple and easy "./configure --prefix=foo &&
> make && make install" from the 2013.2.0.0 HP back in the new HP source
> release.
>
Or equivalent functionality. I don't think we'll be going back to autoconf
& make.


> I hope that I don't sound too negative, you're doing great (and
> unpleasant) work, I just want to make sure that we don't regress on
> Linux platforms...

We need more people involved in the platform!

- Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20140725/36f41713/attachment.html>


More information about the ghc-devs mailing list