On Sun, Sep 16, 2007 at 10:55:43AM +0200, Sven Panne wrote:
> On Sunday 16 September 2007 04:42, Ian Lynagh wrote:
> > At the interface to the outside world (i.e. the configure flags) they
> > have the normal semantics. We then append "/ghc-$(ProjectVersion)" to
> > the internal build system variab
| We definitely support a critical appraisal and overhaul of the
| path-handling and installation machinery,
PS: Sven, thank you *very much* for taking the time to think about the build
system constructively, and to propose solutions. As Simon says, we know it's
not a thing of beauty and we're
Sven Panne wrote:
I don't want to make such changes before 6.8.1 is out, anyway. Let's get this
release out of the door with all necessary hacks, and let's clean up the mess
afterwards.
Hi Sven,
We definitely support a critical appraisal and overhaul of the
path-handling and installation ma
On Sunday 16 September 2007 04:42, Ian Lynagh wrote:
> At the interface to the outside world (i.e. the configure flags) they
> have the normal semantics. We then append "/ghc-$(ProjectVersion)" to
> the internal build system variables. This seems reasonable to me - I
> don't think it would be bette
On Sat, Sep 15, 2007 at 07:48:43PM +0200, Sven Panne wrote:
>
> The first confusing things are that "datadir", "libdir" and "libexecdir"
> don't
> have the proposed GNU semantics. because they contain the package
> name "ghc-XY".
At the interface to the outside world (i.e. the configure flags)
OK, after digging around the build system quite a bit, here is my first
proposal to get things back into a sane state.
The first confusing things are that "datadir", "libdir" and "libexecdir" don't
have the proposed GNU semantics. because they contain the package
name "ghc-XY". They are intende
