From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: Re: custom copies of libraries (was Re: [Caml-list] OCaml Labs)
Date: Tue, 23 Oct 2012 10:47:55 +0900 [thread overview]
Message-ID: <5085F74B.2050908@riken.jp> (raw)
In-Reply-To: <CALdQWQ46M2hUtsscNueW0BD99pLnYJ2JwbrPFTROg1dJQgQEbg@mail.gmail.com>
On 10/21/2012 08:45 PM, Yoriyuki Yamagata wrote:
> 2012/10/21 Ralf Treinen <treinen@free.fr>:
>> avoiding custom copies of libraries that are published independently,
>
> Completely off-topic, but is making custom copies so bad thing? I
> incline to include third-party's libraries into my libraries unless
> the library is too big, so that the my libraries are compiled with
> libraries whose behaviors are tested and guaranteed.
Plus, when you do this, your software can be compiled and run right
after checkout.
> If we have a good package management system, things would be a bit
> different, but still a package management system guarantees only, say,
> that the version numbers of libraries are higher than XXXX, which does
> not preclude many problems.
next prev parent reply other threads:[~2012-10-23 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 11:45 Yoriyuki Yamagata
2012-10-21 13:01 ` Adrien
2012-10-21 15:24 ` Ralf Treinen
2012-10-23 1:47 ` Francois Berenger [this message]
2012-10-28 9:03 ` Richard W.M. Jones
2012-10-28 11:13 ` Yoriyuki Yamagata
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=5085F74B.2050908@riken.jp \
--to=berenger@riken.jp \
--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;
as well as URLs for NNTP newsgroup(s).