From: Sven Luther <sven.luther@wanadoo.fr>
To: Maxence Guesdon <maxence.guesdon@inria.fr>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
skaller@tpg.com.au, 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:21:56 +0100 [thread overview]
Message-ID: <20040121152156.GA7772@iliana> (raw)
In-Reply-To: <20040121155452.459de8f0.maxence.guesdon@inria.fr>
On Wed, Jan 21, 2004 at 03:54:52PM +0100, Maxence Guesdon wrote:
> > > That's what I was thinking about: the mandatory license tag could
> > > take an url and the license would be retrieved from that url when
> > > the caml-get archive is retrieved. If a license could not be
> > > retrieved (because of a wrong url for example), the element would
> > > not be available in the client repository.
> >
> > Notice that many licences mandate that either the full licence or a
> > reduced version is available together with the source you distribute.
>
> Would it be ok it the license was put in the client repository and printed
> with the code when the (for example) -l option is given ? (By default
> the complete license information would not be printed with the code, only
> the url where to find it.) This way the license is available but not
> always added to your file when you want to use an element of the repository
> in your code.
Imagine a guy who ocaml-get's a given bit of code on his laptops, and
then wants to work on it in a plane or somewhere else offline ?
He will then have no access ot the licence, which is not ok.
(But then, i have not looked at your work in detail, and may have missed
something).
The best would be to have, for each bit of source you can ocaml-get, a
link to a licence file, which may be common to many ocaml-gettable
sources, and which get downloaded only if it has not already, maybe with
a md5sum check to make sure it is indeed the same licence.
Then, you can just have the licence tag or whatever refer to a file on
the client harddisk, and there will be no problem.
BTW, how does ocaml-get integrate (or not) with the debian packaging
effort ? Will it be possible to use it to install non-packaged stuff in
a debian policy friendly way or something like that ?
Friendly,
Sven Luther
-------------------
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:22 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 [this message]
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
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=20040121152156.GA7772@iliana \
--to=sven.luther@wanadoo.fr \
--cc=caml-list@inria.fr \
--cc=erayo@cs.bilkent.edu.tr \
--cc=maxence.guesdon@inria.fr \
--cc=skaller@tpg.com.au \
/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