consequences of moving ozmake to stdlib

[Kevin Glynn]

Denys Duchier <duchier at ps.uni-sb.de> writes:


> There are two ways to do this:
> 
>   - either have 2 distinct rpms for core and stdlib - this is simplest
>     and I like having the option to update them independently.  On the
>     other hand, it would take two src rpms for a default distro
>     instead of just one.
> 
>   - or, when building rpms, actually perform an intermediate install
>     of the core to a secondary "fake" root and use that to build
>     ozmake and stdlib.
> 
> The second option means that we can continue using a single src rpm
> for building a default distro.  This is nice because it is simpler for
> members of the community to supply us with binary rpms for various
> linux distros.
> 
> Unless there are objections, I will make modifications to support the
> 2nd option.
> 

My vote too.  We should be aiming that all installations have the
stdlib, much better to bundle core and stdlib in one rpm.

> I will also probably need some help in testing these, as I no longer
> have root access to any rpm based distro.  I will also need help in
> testing on Windows (and possibly MacOS X) - for Windows, the main
> issue, I think, is path robustness.  I moved the cygwin path support
> from the core to the ozmake build, but I have no means of testing
> whether I got it right.

Let us know when you are ready for this testing. Boriss can test on
Mandrake 9.1 and I can try a windows build.

cheers
k