Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Manfred Lotz <manfred.lotz@arcor.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlbuild on Windows and bash vs. cmd
Date: Fri, 14 Oct 2016 14:19:46 +0200	[thread overview]
Message-ID: <20161014141946.74f3ec4e@hogwart.bsdlocal.net> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CF8EF58@IRSMSX102.ger.corp.intel.com>

On Tue, 11 Oct 2016 13:46:28 +0000
"Soegtrop, Michael" <michael.soegtrop@intel.com> wrote:

> Dear Yaron,
> 
> > I hate licenses.  
> 

:-)

> it is definitely a good source of income for lawyers, and I found it
> is worthwhile for a SW developer to take a 1 day course on the topic
> - it is a fairly surprising subject.
> 

Could you point to such a course? 


> I would think it would be best to triple license it under Apache + a
> verbatim copy of the current Ocamllib license (LGPL 2.1 with link
> exception) + "the current or any past license of Ocamllib ". The
> latter would make it easier for the Ocamllib team to change their
> license later. If this helps, I could ask our in house license
> lawyers for advice.
> 
> But I have no idea if there are, besides the license issues, other
> reasons for not having common modules. One is likely the different
> base library, but in this specific case it shouldn't be much of an
> issue.
> 
> 
> One technical note: I would implement in addition to processes
> defined by executables some simple built in standard processes, like
> cp, ln, cat, mkdir, tee (might be a combiner) and later maybe even
> sed, sort, wc, find. It doesn't help to have a portable shell
> environment, if you don't have portable core commands. Compiling "ln"
> for Windows is actually harder than compiling gcc or OCaml. Of cause
> it doesn't make sense to reimplement half of unix, but at least
> simple forms of those commands used in shell scripts every other line
> and which are just a few lines in OCaml would make sense.
> 
> Best regards,
> 
> Michael
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Christin Eisenschmid, Christian Lamprechter
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
> 


  reply	other threads:[~2016-10-14 12:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 13:38 Soegtrop, Michael
2016-10-06 13:45 ` Kakadu
2016-10-06 14:01   ` Soegtrop, Michael
2016-10-06 13:55 ` Daniel Bünzli
2016-10-06 14:15   ` Soegtrop, Michael
2016-10-06 14:45     ` Gabriel Scherer
2016-10-06 16:16       ` Soegtrop, Michael
2016-10-06 17:45 ` Jeremie Dimino
2016-10-06 18:56   ` Gerd Stolpmann
2016-10-07  6:58     ` Soegtrop, Michael
2016-10-07 16:19       ` Yaron Minsky
2016-10-11 11:49         ` Soegtrop, Michael
2016-10-11 12:36           ` Yaron Minsky
2016-10-11 13:00             ` Ivan Gotovchits
2016-10-11 13:06               ` Anil Madhavapeddy
2016-10-11 13:13                 ` Yaron Minsky
2016-10-11 13:27                   ` Hendrik Boom
2016-10-11 13:53                     ` Soegtrop, Michael
2016-10-11 15:48                       ` Adrien Nader
2016-10-11 13:46             ` Soegtrop, Michael
2016-10-14 12:19               ` Manfred Lotz [this message]
2016-10-17  8:08                 ` Soegtrop, Michael
2016-10-17  9:22                   ` Manfred Lotz

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=20161014141946.74f3ec4e@hogwart.bsdlocal.net \
    --to=manfred.lotz@arcor.de \
    --cc=caml-list@inria.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