<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I normally export a custom OPAMROOT environment variable rather than move files around.</div></div></blockquote><div><br class=""></div>Both exportring OPAMROOT and renaming~/.opam should work fine (I think it's cleaner to export OPAMROOT, though).</div><div><br class=""></div><div>Thomas</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">-anil</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 26 Jan 2015, at 14:49, Gabriel Scherer <<a href="mailto:gabriel.scherer@gmail.com" class="">gabriel.scherer@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">opam-devel, is there a recommended fool-proof way to save an opam root before installing another OPAM version to experiment with it, and be able to come back to one's usual environment?<div class=""><br class=""></div><div class="">I'd like to test Jon's packages, but I'm a bit wary of losing/corrupting the dozen of switches I have already. I'm thinking of basically</div><div class=""> mv ~/.opam ~/.opam.bak</div><div class=""> <uninstall my opam></div><div class=""> <try the packages then uninstall them></div><div class=""> mv ~/.opam.bak ~/.opam</div> <reinstall my opam><div class=""><br class=""></div><div class="">If there is nothing wrong with this approach, it might be useful to document it somewhere -- it's not in the developer manual for example. This could be useful when asking users to test beta-releases of OPAM as well (I know I was unhappy when I tested 1.2 and my repository format was silently updated to 1.2, making it harder to go back).</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Jan 26, 2015 at 3:16 PM, Jon Ludlam <span dir="ltr" class=""><<a href="mailto:jonathan.ludlam@citrix.com" target="_blank" class="">jonathan.ludlam@citrix.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br class="">
<br class="">
I'd like to ask for help with testing the RPMs I've built for opam<br class="">
for Fedora.<br class="">
<br class="">
I've submitted a some review requests to get opam into Fedora. This has<br class="">
involved getting 6 other packages into RPMs as there was pushback on<br class="">
using the bundled libraries as part of the RPM<br class="">
(<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1060436" target="_blank" class="">https://bugzilla.redhat.com/show_bug.cgi?id=1060436</a>). These are going<br class="">
through the usual process of being reviewed, but I thought it would be<br class="">
useful to test them from a functional perspective too. The top-level<br class="">
review request is here:<br class="">
<br class="">
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1185099" target="_blank" class="">https://bugzilla.redhat.com/show_bug.cgi?id=1185099</a><br class="">
<br class="">
For ease of testing, I have built them using copr, Fedora's build<br class="">
service, and the RPMs can be installed directly from there. There<br class="">
are instructions on how to do that on the project page:<br class="">
<br class="">
<a href="https://copr.fedoraproject.org/coprs/jonludlam/opam/" target="_blank" class="">https://copr.fedoraproject.org/coprs/jonludlam/opam/</a><br class="">
<br class="">
I'd be really grateful if anyone had a few minutes to look and see if<br class="">
there's anything obviously wrong with them.<br class="">
<br class="">
Thanks a lot!<br class="">
<br class="">
Jon<br class="">
<br class="">
_______________________________________________<br class="">
opam-devel mailing list<br class="">
<a href="mailto:opam-devel@lists.ocaml.org" class="">opam-devel@lists.ocaml.org</a><br class="">
<a href="http://lists.ocaml.org/listinfo/opam-devel" target="_blank" class="">http://lists.ocaml.org/listinfo/opam-devel</a><br class="">
</blockquote></div><br class=""></div>
_______________________________________________<br class="">opam-devel mailing list<br class=""><a href="mailto:opam-devel@lists.ocaml.org" class="">opam-devel@lists.ocaml.org</a><br class=""><a href="http://lists.ocaml.org/listinfo/opam-devel" class="">http://lists.ocaml.org/listinfo/opam-devel</a><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">opam-devel mailing list<br class=""><a href="mailto:opam-devel@lists.ocaml.org" class="">opam-devel@lists.ocaml.org</a><br class="">http://lists.ocaml.org/listinfo/opam-devel<br class=""></div></blockquote></div><br class=""></body></html>