From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by sympa.inria.fr (Postfix) with ESMTPS id AC43E7EC41 for ; Sun, 21 Oct 2012 07:42:37 +0200 (CEST) Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of fabrissimo@gmail.com) identity=pra; client-ip=209.85.219.54; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="fabrissimo@gmail.com"; x-sender="fabrissimo@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail4-smtp-sop.national.inria.fr: domain of fabrissimo@gmail.com designates 209.85.219.54 as permitted sender) identity=mailfrom; client-ip=209.85.219.54; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="fabrissimo@gmail.com"; x-sender="fabrissimo@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-oa0-f54.google.com) identity=helo; client-ip=209.85.219.54; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="fabrissimo@gmail.com"; x-sender="postmaster@mail-oa0-f54.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhQCAIyKg1DRVds2m2dsb2JhbABEwQgIIwEBAQEBCAkLCRQngiABAQEDARICLAE4AQMBCwEFBQsDCi4hARIBBQEcBhMih1ADCQadDQkDjx6EGScNiU4BBQyKamkFIoZIA5QcgVWLKYMvFimBWII7gVo X-IronPort-AV: E=Sophos;i="4.80,624,1344204000"; d="scan'208";a="159785621" Received: from mail-oa0-f54.google.com ([209.85.219.54]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 21 Oct 2012 07:42:36 +0200 Received: by mail-oa0-f54.google.com with SMTP id n9so2787780oag.27 for ; Sat, 20 Oct 2012 22:42:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ni/qm9zYdxIitU7ExvaGX+exUFwWS/ozbcGw7Gx6DHY=; b=FRG1F1R7dTeayPFrNOvw7vSnTtxfYnrYQscWxDaOv5zq73eNM4QdNYrh0CQR3B5Dcn JNOQnyPvOk0auwKr9wC0sXzNJgULCe4knDMS1sukTBSzhnmjvKm5Mx38bseun1OridU9 6nw6etZ+GaLjR3vA5Q66350NuELQulPvKxdlLSCkmWvHap3rSGGQKdjHfb5a6BNdVwF8 ansMsDedjYRAAFK6zkKcwi5ABCcu5ZiD7zRovzbs32CQ+BN80peniEILDzRTHNIykCt0 m2Te91/HwGRVWISKQDA3SHV0TWR9c51jDjqyiqif4JRDkqNCLn177OenBvmhX5HV+a6K NHjw== MIME-Version: 1.0 Received: by 10.182.5.168 with SMTP id t8mr4125942obt.32.1350798155251; Sat, 20 Oct 2012 22:42:35 -0700 (PDT) Sender: fabrissimo@gmail.com Received: by 10.76.25.169 with HTTP; Sat, 20 Oct 2012 22:42:35 -0700 (PDT) In-Reply-To: References: <20121020211042.GE5986@dark.recoil.org> Date: Sun, 21 Oct 2012 07:42:35 +0200 X-Google-Sender-Auth: YrHF5rN0Pll4cVc-c_uyXe7BUro Message-ID: From: Fabrice Le Fessant To: Paolo Donadeo Cc: OCaml mailing list Content-Type: text/plain; charset=ISO-8859-1 X-Validation-by: fabrissimo@gmail.com Subject: Re: [Caml-list] OCaml Labs Hi, I should stress that there has been no official announce of OPAM, because it is still considered as unstable, but it should be officially released soon... One of the major differences with other package managers for OCaml for me is its ability to maintain different trees, for different versions of the compiler, allowing to test easily a new version or a patch. On Sun, Oct 21, 2012 at 1:38 AM, Paolo Donadeo wrote: > A question: can OPAM live in peace with odb.ml or GODI? In this moment > my environment is built with GODI (for compiler and major libraries) > and what is not present in GODI is installed with odb.ml, which > installs everything in ~/.odb, no conflict with /opt/godi/... OPAM installs its packages in ~/.opam/, so there will be no conflict in the installation. > Can I > say to OPAM to ignore a dependency, for example can I install an OPAM > package which depends on Batteries, while Batteries installed with > GODI? The purpose of OPAM is to manage the versions of installed packages, so that if some package needs a new version of another package, it would be able to upgrade that package. If some packages are managed outside of OPAM, it will not be able to upgrade them, and upgrading them with another package manager will break the consistency between the packages. So, you probably don't want to do that. Packaging a library for OPAM is quite simple (you just need to explain how to build it, i.e. usually ./configure; make; make install), and the repository is available on Github, so uploading a package is just sending a pull-request there... --Fabrice