CustomBuild 1.1.16 and 1.2.10

smtalk

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
10,628
Location
LT, EU
Many new features and bugfixes, huge code clean-up :)
Changelog:
* Merged doVersions() and doVersionsUpdate().
* Added setOpt() function. So, now options can be changed this this way: ./build set option_name value.
* Dramatic speed improvement on servers with more than 1 CPU (using make -j cores instead of make for Apache, PHP and exim).
* It's now possible to use custom apache configuration files (just place them in custom/ap1(or 2)/conf.
* Support for FreeBSD 7.1.
* More 'silent' RoundCube installation.
* If default PHP is installed as CGI - .'/build squirrelmail/roundcube/atmail/uebimiau' doesn't chown any files/folders to apache user.
* Fixed MySQL installation bug on Debian systems. If MySQL package is not downloaded - script does not try to install it.
​
These versions should be uploaded to DA servers soon. If you want to try them now:
1.1.16
Code: 
cd /usr/local/directadmin/custombuild
wget -O build http://www.custombuild.eu/build-1.1.16
1.2.10
Code: 
cd /usr/local/directadmin/custombuild
wget -O build http://www.custombuild.eu/build-1.2.10
 
Not Found
The requested URL /build-1.1.16 was not found on this server.
 
Try again :) It was named after 1.1.17 (mistype..), sorry.
 
Might want to change:

Code: 
if [ "`cat /proc/cpuinfo | grep 'core id' | wc -l`" -gt 0 ]; then
	CPU_CORES="`cat /proc/cpuinfo | grep 'core id' | wc -l`"
fi

To:

Code: 
if [ -f /proc/cpuinfo ]; then
	if [ "`cat /proc/cpuinfo | grep 'core id' | wc -l`" -gt 0 ]; then
		CPU_CORES="`cat /proc/cpuinfo | grep 'core id' | wc -l`"
	fi
fi

Because we get "cat: /proc/cpuinfo: No such file or directory" on FreeBSD.

Also noticed a ./build update drops it back to 1.1.15
 
Last edited:
scsi said:
Might want to change:

Code: 
if [ "`cat /proc/cpuinfo | grep 'core id' | wc -l`" -gt 0 ]; then
    CPU_CORES="`cat /proc/cpuinfo | grep 'core id' | wc -l`"
fi
To:

Code: 
if [ -f /proc/cpuinfo ]; then
    if [ "`cat /proc/cpuinfo | grep 'core id' | wc -l`" -gt 0 ]; then
        CPU_CORES="`cat /proc/cpuinfo | grep 'core id' | wc -l`"
    fi
fi

Because we get "cat: /proc/cpuinfo: No such file or directory" on FreeBSD.
Click to expand...

It's not a huge problem (you can ignore it). I'll add "sysctl -a | grep cpu" for FreeBSD soon.
scsi said:
Also noticed a ./build update drops it back to 1.1.15
Click to expand...
That's normal, because 1.1.16 is not on DA servers yet.
 
Amazing release smtalk, the cores thing will surely help on building on new machines (I guess a lot of people here have at least dual core)
 
Thank you smtalk! Greata script. Made my life much easier!

Just a note:


#./build update
Click to expand...
switched my custombuild back to 1.2.9

i think it could go with 1.2.10 because its stable now!
 
AxlF, thanks.

Both 1.1.16 and 1.2.10 have been uploaded to DA servers.
 
I didn't tell you it has been uploaded to custombuild.eu :) But per your request it's there now.
 
I update van 1.1.18 to 1.2.10 but i got an error..

wget -O build http://www.custombuild.eu/build-1.2.10
--09:16:37-- http://www.custombuild.eu/build-1.2.10
Resolving www.custombuild.eu... 77.79.12.73
Connecting to www.custombuild.eu|77.79.12.73|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 216688 (212K) [text/plain]
Saving to: `build'

100%[=====================================================>] 216,688 359K/s in 0.6s

09:16:42 (359 KB/s) - `build' saved [216688/216688]
[root@custombuild]# ./build
Wrong php_ini_type set in options.conf.

What wrong with the php ini type?
 
If you want to upgrade 1.1 to 1.2 then set custombuild=1.2 in the options.conf. Set php_ini_type=recommended.
 
smtalk said:
If you want to upgrade 1.1 to 1.2 then set custombuild=1.2 in the options.conf. Set php_ini_type=recommended.
Click to expand...

Change the version from 1.1 to 1.2 but no it doesnt work anymore at all.. :(

Oke redownloaded the 1.20.10 and if i run it now it says:

[root@ custombuild]# ./build
Can not install PHP6 and PHP5 as CLI.

What am i doing wrong? Is 1.2 still beta or should ik stick to 1.1?
 
Last edited:
You must log in or register to reply here.
Back
Top