[glick2] Update README with new prefix



commit 42791dda24b85d61596782d9db9132a341846842
Author: Alexander Larsson <alexl redhat com>
Date:   Tue Nov 22 14:46:45 2011 +0100

    Update README with new prefix

 README |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/README b/README
index 6c4b2ac..06f447b 100644
--- a/README
+++ b/README
@@ -61,7 +61,7 @@ the bundle to be mounted (by opening ~/.glick/socket and passing the open
 fd to it), and then the setuid helper $libexecdir/glick-helper creates
 a new mount namespace for the bundle process and binds mounts /opt/bundle to
 the ~/.glick/<subdir> where the bundle gets mounted. This means you can
-build your bundles with a static prefix of /opt/bundle and each bundle
+build your bundles with a static prefix of /opt/bundle/data and each bundle
 instance will see its files there. When the last process in the bundle
 exits the bundle will automatically be unmounted.
 
@@ -78,12 +78,12 @@ inside glick that will automatically do things like rebuild icon caches and
 mime databases when files are added in the right directories.
 
 So, a typical bundle creation would be something like:
-./configure --prefix=/opt/bundle
+./configure --prefix=/opt/bundle/data
 make
 make install DESTDIR=/tmp
 glick-mkbundle -i org.gnome.App -v 1.1.2 -e bin/the_app \
    -E /share/mime-info -E /share/icons -E /share/applications \
-   /tmp/opt/bundle app.bundle
+   /tmp/opt/bundle/data app.bundle
 
 Although, ideally when building a set of bundles common binaries for
 dependencies should be used to maximize file sharing between bundles.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]