Re: extra release step

> From: Thien-Thi Nguyen [email protected]

> Here are the two courses:
> =

> - Nobody cares any more about mingwin.
> =A0 =3D> Great!=A0 I'll gladly fully decruft and carry on "normally".
> =A0 =A0 By "fully", i mean remove ALL infrastructure and code.
> =A0 =A0 By "gladly", i mean with unicorns dancing and bird singing...
> =

> - Someone can muster a cygwin build to provide the template files.
> =A0 =3D> OK, i suggest the procedure:
> =A0 =A0 =A0 - ttn does "normal" (but invalid for mingwin) "make =

> dist"
> =A0 =A0 =A0 =A0 under GNU/Linux
> =A0 =A0 =A0 - someone else unpacks this provisional tarball,
> =A0 =A0 =A0 =A0 builds/tests on cygwin then does "make dist" again
> =A0 =A0 =A0 - we publish THAT tarball as the official one
> =A0 =A0 If this procedure is not palatable, what others would do?
> =A0 =A0 Another idea is try this for 0.2.x, and then drop mingwin
> =A0 =A0 completely for 0.3.x.
> =

> What do people think?

I don't remember the whole dependency list of the top of my head,
but, I think that Guile is not very portable.=A0 I know that there
is no official working Guile 2.0.x on mingw or cygwin, although
there have been unofficial Guile releases for mingw and cygwin
by other parties.

But in any case, there is no reason why the Guile support on
Serveez need compile on mingw and cygwin for those versions of
Guile that don't have official cygwin and mingw ports.

-Mike Gran