From: Alessandro Baretta <alex@baretta.com>
To: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] CDK with Ocaml 3.06 (fwd)
Date: Tue, 15 Oct 2002 07:02:31 +0200 [thread overview]
Message-ID: <3DABA167.5060204@baretta.com> (raw)
In-Reply-To: <20021015044203.GA1016@iliana>
Sven LUTHER wrote:
> On Tue, Oct 15, 2002 at 12:44:57AM +0200, Gerd Stolpmann wrote:
>
>>- Authors usually cannot test source packages on lots of platforms. Problems
>> range from /bin/sh incompatibilities to the Unix/Windows nightmare. Especially
>> for the latter I really don't know how to cope with it, because porting
>> Makefiles and scripts to Windows is time-intensive, and as a Unix fan
>> I have the attitude "let the Windows users do it".
>
>
> At least for the windows solution, i strongly think a binary
> distribution mechanism is what is needed for the users and also would
> save a lot of time and 'howto build' kind of questions on the mailing
> lists. There is no reason not to do so, i am no windows expert, but
> windows offer a stable set of libraries and other system component that
> can be relied upon to install ocaml binary packages upon. This already
> works for ocaml itself.
>
Very true, but I have a feeling most users/developers are on
'nixes and don't really give a dime about Windows. I expect
most people to be willing to release their working
sources--working on their flavor of unix--but not to work on
creating a Windows distro, be it source or binary. I also
don't expect anyone, say, of the Debian folks, to pick up
the Windows-port crusage single-handedly.
Let's just say this is a pretty nasty topic. I have a
feeling that the only solution would be to have an official
O'Caml IDE à la DevStudio--eeek!--capable of handling
compilation and packaging in just the right way wherever
it's used, without resorting to such unix tools as /bin/sh,
configure, make and whatnot, but this would fit better in a
commercial project than in an open source project.
The other solution is to start using Windows installation
discs for what there best at: saving your tablecloth from
beer stains...
Alex
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-10-15 4:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 16:42 Alain Frisch
2002-10-14 17:39 ` Stefano Zacchiroli
2002-10-14 17:59 ` Alain Frisch
2002-10-14 18:16 ` Sven LUTHER
2002-10-14 20:38 ` Pierre Weis
2002-10-14 21:07 ` Sven LUTHER
2002-10-14 22:44 ` Gerd Stolpmann
2002-10-15 4:42 ` Sven LUTHER
2002-10-15 4:53 ` Chris Hecker
2002-10-15 5:15 ` Sven LUTHER
2002-10-15 5:25 ` Chris Hecker
2002-10-15 5:41 ` Sven LUTHER
2002-10-15 6:34 ` Chris Hecker
2002-10-15 5:02 ` Alessandro Baretta [this message]
2002-10-15 5:04 ` Chris Hecker
2002-10-15 5:08 ` Sven LUTHER
2002-10-17 17:57 ` Gleb N. Semenov
2002-10-15 11:21 ` Sign the packages (was Re: [Caml-list] CDK with Ocaml 3.06 (fwd)) Tim Freeman
2002-10-15 11:59 ` Sven Luther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DABA167.5060204@baretta.com \
--to=alex@baretta.com \
--cc=caml-list@inria.fr \
--cc=luther@dpt-info.u-strasbg.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).