From: Thomas Gazagnaire <thomas@ocamlpro.com>
To: "Sébastien Dailly" <sebastien-ocaml@chimrod.com>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: ~/.opam design
Date: Thu, 30 May 2013 09:38:09 +0200 [thread overview]
Message-ID: <85FC58B0-BA1E-49C0-9380-802315C81592@ocamlpro.com> (raw)
In-Reply-To: <3da55d6fccc845346c96c7af502cc706@chimrod.com>
> Maybe is the subject now closed, and I'm answering too late, but I'll greatly appreciate if opam could follow the XDG Directory design[1] :
>
> $XDG_CONFIG_HOME/opam (default ~/.config/opam) for the configuration
> $XDG_DATA_HOME/opam (default ~/.local/opam) for the package and all datas
>
> This allow to stop the polution in the users ~ , and give the user a way to define it's own path.
>
> [1] http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
The subject is not closed at all, and we might move in this direction in future releases of OPAM. See for instance [1]
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). 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. Luckily, all the paths used by OPAM are defined in [4] so they can be changed without too much hassle.
Best,
Thomas
[1] https://github.com/OCamlPro/opam/issues/401
[2] https://github.com/OCamlPro/opam/issues/398
[3] https://github.com/OCamlPro/opam-repository/issues/746
[4] https://github.com/OCamlPro/opam/blob/master/src/core/opamPath.ml
next prev parent reply other threads:[~2013-05-30 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 21:29 Florent Monnier
2013-05-30 7:18 ` Sébastien Dailly
2013-05-30 7:38 ` Thomas Gazagnaire [this message]
2013-05-30 8:14 ` Sébastien Dailly
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=85FC58B0-BA1E-49C0-9380-802315C81592@ocamlpro.com \
--to=thomas@ocamlpro.com \
--cc=caml-list@inria.fr \
--cc=sebastien-ocaml@chimrod.com \
/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).