<html>
<head>
<meta content="text/html; charset=windows-1255"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Micha,<br>
<br>
comments inline:<br>
<br>
On 12/24/2012 10:36 AM, Micha Silver wrote:<br>
</div>
<blockquote cite="mid:50D81409.2020908@arava.co.il" type="cite">
<pre wrap="">Hi Angelos:
Again thanks for the tips.
I'm re-reading the wiki page on the build process. A few more questions, if I
may, just to be sure I understand the steps:
1- I understand that any ubuntu (or Debian?) system can be used now to do a
build? Just grab and run the bootstrap.sh, which pulls down all the gisvm
scripts etc. Is that right? This I do only once?</pre>
</blockquote>
Basically you can build using a debian or ubuntu but there are some
details that differentiate the build result (eg when building under
Ubuntu, Plymouth does not work as expected) The best result is
achieved when you use the following base system:<br>
- Xubuntu 32bit base with SAME kernel version as the Xubuntu iso (if
you want updates use apt-get upgrade instead of apt-get <br>
dist-upgrade)<br>
- User account to run the build script should be "user" since this
account will be used during chroot to run the scripts. We do that to
keep backward compatible scripts and not be forced to rewrite them
all from scratch.<br>
<br>
About bootstrap, yes you only need it once and then you can svn up
and rerun the build as many times as you like.<br>
<br>
For building the official disk I use a base VM and change it only
when we change kernel. <br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1255">
<blockquote cite="mid:50D81409.2020908@arava.co.il" type="cite">
<pre wrap="">
2- Then I run the ~/gisvm/bin/build_chroot.sh to get a default
osgeo-live_xxx.iso under my <user>/livedvdtmp directory?</pre>
</blockquote>
Yes<br>
<blockquote cite="mid:50D81409.2020908@arava.co.il" type="cite">
<pre wrap="">
3- Now I can alter scripts in the ~/gisvm/bin directory (especially the
inchroot.sh) to add/remove whatever I need? And If I now re-run the
build_chroot.sh, my customizations will be applied?</pre>
</blockquote>
We have a build_chroot_debug.sh to help you enable and disable
packages and make smaller tests, rather than building the whole iso
each time. Just make sure to enable the packages you need as
dependencies. This script will be copied in the chroot environment
and be used. Caution: the scripts are not moved into chroot, they
are svn checkedout from within the chroot, so any change you do on a
project script should be copied manually by you or committed in
order to be tested.<br>
<blockquote cite="mid:50D81409.2020908@arava.co.il" type="cite">
<pre wrap="">
4- I see that the whole <user>/livedvdtmp/edit directory is emptied after each
run of build_chroot.sh. Does it make sense to leave that directory as is, in
order to ease bandwidth use on each re-run of the build_chroot?</pre>
</blockquote>
This folder will be deleted and recreated on next run.<br>
I wanted to implement this feature (keeping the installation files
to be reused) but I did not have the time so far...<br>
<blockquote cite="mid:50D81409.2020908@arava.co.il" type="cite">
<pre wrap="">
Cheers,
Micha
</pre>
</blockquote>
Cheers,<br>
Angelos<br>
<br>
<pre class="moz-signature" cols="72">--
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
<a class="moz-txt-link-freetext" href="http://users.ntua.gr/tzotsos">http://users.ntua.gr/tzotsos</a></pre>
</body>
</html>