From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 19CBB7EE51 for ; Thu, 30 May 2013 10:14:54 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of sebastien-ocaml@chimrod.com) identity=pra; client-ip=212.27.42.1; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="sebastien-ocaml@chimrod.com"; x-sender="sebastien-ocaml@chimrod.com"; x-conformance=sidf_compatible Received-SPF: PermError (mail2-smtp-roc.national.inria.fr: cannot correctly interpret sender authenticity information from domain of sebastien-ocaml@chimrod.com) identity=mailfrom; client-ip=212.27.42.1; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="sebastien-ocaml@chimrod.com"; x-sender="sebastien-ocaml@chimrod.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@smtp1-g21.free.fr) identity=helo; client-ip=212.27.42.1; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="sebastien-ocaml@chimrod.com"; x-sender="postmaster@smtp1-g21.free.fr"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvMAAOMJp1HUGyoBk2dsb2JhbABZhnS6dXCCanoWDgEBAQEHCwsJFAMlgiMBAQQBIw8BBTYLBQsEBxoCGA4CAiwrBhuHfwqnYpIXgSaHaoYDB4JDgRQDrAw X-IPAS-Result: AvMAAOMJp1HUGyoBk2dsb2JhbABZhnS6dXCCanoWDgEBAQEHCwsJFAMlgiMBAQQBIw8BBTYLBQsEBxoCGA4CAiwrBhuHfwqnYpIXgSaHaoYDB4JDgRQDrAw X-IronPort-AV: E=Sophos;i="4.87,769,1363129200"; d="scan'208";a="19583818" Received: from smtp1-g21.free.fr ([212.27.42.1]) by mail2-smtp-roc.national.inria.fr with ESMTP; 30 May 2013 10:14:53 +0200 Received: from goku.chimrod.com (unknown [88.172.128.238]) by smtp1-g21.free.fr (Postfix) with ESMTP id D0CB19400BA; Thu, 30 May 2013 10:14:48 +0200 (CEST) Received: by goku.chimrod.com (Postfix, from userid 33) id 4C6581FC7D; Thu, 30 May 2013 10:14:47 +0200 (CEST) To: Thomas Gazagnaire X-PHP-Originating-Script: 0:main.inc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Thu, 30 May 2013 10:14:47 +0200 From: =?UTF-8?Q?S=C3=A9bastien_Dailly?= Cc: In-Reply-To: <85FC58B0-BA1E-49C0-9380-802315C81592@ocamlpro.com> References: <3da55d6fccc845346c96c7af502cc706@chimrod.com> <85FC58B0-BA1E-49C0-9380-802315C81592@ocamlpro.com> Message-ID: X-Sender: sebastien-ocaml@chimrod.com User-Agent: Roundcube Webmail/0.7.2 Subject: Re: [Caml-list] Re: ~/.opam design Le 2013-05-30 09:38, Thomas Gazagnaire a écrit : > > The subject is not closed at all, and we might move in this direction > in future releases of OPAM. See for instance [1] Thanks for pointing the issue. I answerd on the mailing list without consulting the project site. > > The current design has a lot of advantages (the main one being that > you can remove your ~/.opam if you want restart from scratch) and it > can be tweaked to have a global installation (see [2,3], even if the > tweak is not very well documented). Each application has a good reason for beiing installed directly in the ~ directory. But in a deskop usage (server is different), this finaly create a big polution in the user directory. The xdg try to define a general usage for preventing this. > But yes, for some configurations > (such as shared NFS homedirs), the current situation is not perfect > and it would be nice to be able to separate the data from the > configuration bits. This is a more general problem : exporting the configuration from one site to another one, or versionning the opam conf in a production server is greatly facilitated if the configuration is located in a dedicated path. > Luckily, all the paths used by OPAM are defined in > [4] so they can be changed without too much hassle. The main advantage I can see with the xdg path is that the configuration path is declared before installing anything, and can be configured once for a whole system. This allow to configure differents workspace just by sourcing a bash file ; as I can do with findlib and ${OCAMLFIND_CONF} I think you can get as many pros as cons, but today, the xdg path is a standard in a desktop… Regards, -- Sébastien