Differences

This shows you the differences between two versions of the page.

--- developers:fallbacks_contrib [2017/11/07 15:01] – Yann Pouillon
+++ build:fallbacks_contrib [2018/03/01 17:07] – [Hacking the fallbacks] Yann Pouillon
@@ Line 1: / Line 1: @@
 ====== Hacking the fallbacks ======
-<WRAP important>**IMPORTANT NOTE** \\ We only provide support for the fallbacks delivered through the Abinit Website. If you modify them, we suppose that you know what you are doing and are a sufficiently skilled programmer to solve most issues by yourself. We may be able to help you to a limited extent, but you have to remember that we are developers of Abinit, **NOT** of its fallbacks. An infinitely better way to address your issues will be to collaborate directly with the developers of the relevant projects. Some of us can however send you a quote if you insist on working with Abinit developers only.</WRAP>
+<WRAP important>**IMPORTANT NOTE** \\ We only provide support for the fallbacks delivered through the Abinit Website. If you modify them, we suppose that you know what you are doing and are a sufficiently skilled programmer to solve most issues by yourself. We may be able to help you to a limited extent, but you have to remember that we are developers of Abinit, **NOT** of its fallbacks. An infinitely better way to address your issues will be to collaborate directly with the developers of the relevant projects. Some of us can however send you a quote if working with Abinit developers is mandatory for you.</WRAP>
 ===== Prerequisites =====
@@ Line 58: / Line 58: @@
   - Run //./quicktest.sh// from the top source directory and fix the issues until it succeeds.
   - Install the new fallbacks on your computer and test Abinit with them.
-  - Go back to step 2 until step 3 succeeds.
+  - Go back to step 2 until step 4 succeeds.
   - Request a deployment on the test farm, specifying the branch and its commit checksum.
   - Set your Abinit branch to use the new fallbacks and push it.