caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Maxence Guesdon <maxence.guesdon@inria.fr>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: 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 17:03:18 +0100	[thread overview]
Message-ID: <20040121170318.246e21e5.maxence.guesdon@inria.fr> (raw)
In-Reply-To: <20040121155752.GA8564@iliana>


> > In fact, I was thinking of the following algorithm:
> > - the client does
> >   caml-get update http://foo.bar/archive.cga
> > - then caml-get retrieves the archive, and for each element, look at the
> >   url of the license, retrieves it, and store it in the client repository,
> >   making it available to the use even when he/she is offline.
> 
> It should either not download the archive or put a fat warning if the
> licence is not retrievable, but i think this is already your intention.

Yes. "Je dirais même plus", when downloading an archive, only the elements whose
license can be retrieved will be added to the client repository. 
 
> > Caml-get is done to help the developer, by making use of *pieces* of
> > code easier, thus not making his/her software depend on a library if it only
> > uses one or two functions of this library for example. This can be seen
> > as way to distribute a software which otherwise would depend on a
> > hard-to-install or no-packaged software.
> > 
> > But if a software heavily uses a library, it should rather really depend on
> > this lib (that is: link with it) rather than use caml-get to copy-paste
> > all the library.
> > 
> > Does it answer your question ?
> 
> Well, i was thinking of some way of automatically or semi-automatically
> transforming a bit of caml-getted source into a proper debian package.

I don't think so, then. caml-get has no information about how to compile,
where to install,..., and is not intented to, since it is not a replacement
for the "traditional" way of distributing code.

- 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 16:03 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 [this message]
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=20040121170318.246e21e5.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).