[pitivi] build: Make sure sandbox paths are set before any path set by the user

[Thibault Saunier <tsaunier src gnome org>]

commit 176091fb1de6180d6144b3b9aa164ed58002b28b
Author: Thibault Saunier <tsaunier gnome org>
Date:   Tue Jul 19 08:53:44 2016 -0400

    build: Make sure sandbox paths are set before any path set by the user
    
    Otherwise we might be using component from user local path inside the
    sandbox which should not happen.
    
    And minor fix in docs/HACKING.md

 build/flatpak/enter-env |    2 +-
 docs/HACKING.md         |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/build/flatpak/enter-env b/build/flatpak/enter-env
index ab42424..559a820 100755
--- a/build/flatpak/enter-env
+++ b/build/flatpak/enter-env
@@ -3,7 +3,7 @@
 PITIVI_DIR=$(realpath $(dirname $0)/../../)
 
 function generate_path_and_completion_calls {
-  echo "export PATH=$PITIVI_DIR/bin/:\$PATH"
+  echo "export PATH=$PITIVI_DIR/bin/:/app/bin/:/usr/bin/:\$PATH"
   echo "export CC='ccache gcc'"
   echo "export CXX='ccache g++'"
 }
diff --git a/docs/HACKING.md b/docs/HACKING.md
index 6f8bf6e..8ba0aeb 100644
--- a/docs/HACKING.md
+++ b/docs/HACKING.md
@@ -27,7 +27,7 @@ $ source bin/pitivi-env
 Run `pitivi` while inside the environment to launch Pitivi. Next you should run the unittests.
 ```
 (ptv-flatpak) $ pitivi
-(ptv-flatpak) $ nosetests tests/test_*.py
+(ptv-flatpak) $ make check
 ```
 
 After you hack the source code simply run `pitivi` again to see how your changes work.