From: Maxence Guesdon <maxence.guesdon@inria.fr>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: skaller <skaller@tpg.com.au>,
Sven Luther <sven.luther@wanadoo.fr>,
erayo@cs.bilkent.edu.tr, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Caml-get 0.1
Date: Wed, 21 Jan 2004 16:53:09 +0100 [thread overview]
Message-ID: <20040121165309.2e641520.maxence.guesdon@inria.fr> (raw)
In-Reply-To: <20040121153328.GA8134@iliana>
On Wed, 21 Jan 2004 16:33:29 +0100
Sven Luther <sven.luther@wanadoo.fr> wrote:
> On Thu, Jan 22, 2004 at 02:23:04AM +1100, skaller wrote:
> > On Thu, 2004-01-22 at 01:35, Sven Luther wrote:
> > > On Wed, Jan 21, 2004 at 03:18:33PM +0100, Maxence Guesdon wrote:
> >
> > > Notice that many licences mandate that either the full licence or a
> > > reduced version is available together with the source you distribute.
> >
> > I think that is easily solved as Maxence suggested.
> >
> > The problem is that some licences require that the
> > licence or a reduced version of it *also* occur
> > in every source file, and not just as a separate
> > document in the distribution.
>
> Well, but at least the licence should be put in every source tarball or
> something, and i believe it is good that each individual file also comes
> with a single line telling the licence that is used and where to find
> it.
caml-get could have an option to add or remove the license content
for the caml-get elements in the .ml of .mli files. This way, you
work with no license information in your code, not to pollute your
file when you edit it, and when you're ready to distribute it, you
add the license information with one caml-get command.
What do you think of this ?
Another way could be for caml-get to generate LICENSE1, LICENSE2, ..., files
and add a reference to these files in the inserted code.
Friendly,
- Maxence
-------------------
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:[~2004-01-21 15:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 16:42 Maxence Guesdon
2004-01-20 1:15 ` skaller
2004-01-20 2:37 ` Eray Ozkural
2004-01-20 10:12 ` Maxence Guesdon
2004-01-21 13:59 ` skaller
2004-01-21 14:18 ` Maxence Guesdon
2004-01-21 14:35 ` Sven Luther
2004-01-21 14:54 ` Maxence Guesdon
2004-01-21 15:21 ` Sven Luther
2004-01-21 15:42 ` Maxence Guesdon
2004-01-21 15:57 ` Sven Luther
2004-01-21 16:03 ` Maxence Guesdon
2004-01-21 15:23 ` skaller
2004-01-21 15:33 ` Sven Luther
2004-01-21 15:45 ` skaller
2004-01-21 15:53 ` Maxence Guesdon [this message]
2004-01-21 16:09 ` Sven Luther
2004-01-20 10:11 ` Maxence Guesdon
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=20040121165309.2e641520.maxence.guesdon@inria.fr \
--to=maxence.guesdon@inria.fr \
--cc=caml-list@inria.fr \
--cc=erayo@cs.bilkent.edu.tr \
--cc=skaller@tpg.com.au \
--cc=sven.luther@wanadoo.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).