caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Maxence Guesdon <maxence.guesdon@inria.fr>
To: skaller@tpg.com.au
Cc: erayo@cs.bilkent.edu.tr, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Caml-get 0.1
Date: Wed, 21 Jan 2004 15:18:33 +0100	[thread overview]
Message-ID: <20040121151833.67a29f5c.maxence.guesdon@inria.fr> (raw)
In-Reply-To: <1074693590.11497.16.camel@localhost.localdomain>

On 22 Jan 2004 00:59:51 +1100
skaller <skaller@tpg.com.au> wrote:

> On Tue, 2004-01-20 at 21:12, Maxence Guesdon wrote:
> > On Tue, 20 Jan 2004 04:37:30 +0200
> > > I guess licensing is for people to worry about, not programs :)
> > 
> > But providing an easy way to indicate the license is important, I think,
> > -> the @license tag I want to add.
> 
> Some licences .. most licences unfortunately ..
> create problems for such fine granularity.
> Technically to 'element-get' a single element 
> which is a 3 line function .. you'd have to include
> the whole licence blurb of 60 lines or whatever.
> 
> In interscript (my literate progamming/packaging system),
> I created some mechanism in which a single copy of each 
> required licence could be shipped with a package..
> but the licences were never included in the actual sources.
> [The typeset output contained a link to the file for html,
> or a reference for latex, etc ..).
> 
> Anyhow, when you 'element-get' an element, you probably
> have to ensure the element is
> 
> (a) at least tagged in the fragment source with the licence name
> (b) a copy of the required notice is fetched as well
> 
> .. even if the whole notice isn't included with each element.

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.

- 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


  reply	other threads:[~2004-01-21 14:18 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 [this message]
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
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=20040121151833.67a29f5c.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 \
    /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).