sablink/devkit
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[builder] adding notes on why we do safe_call during equo install phases

Browse Source
This commit is contained in:
mudler
2016-03-29 12:18:07 +02:00
parent 1e993271ec
commit 330eb6faef
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
builder
+2 -2
View File
@@ -286,14 +286,14 @@ if ($use_equo) {
say "", "[install] Those dependencies will be installed with equo :",
@packages_deps, "";
if ($equo_split_install) {
safe_call("equo i --bdeps $_") for ( @packages_deps, @equo_install );
safe_call("equo i --bdeps $_") for ( @packages_deps, @equo_install ); ## bail out here, if installs fails. emerge will compile a LOT of stuff
if ( @equo_remove > 0 ) {
system("equo rm --nodeps $_") for (@equo_remove);
}
}
else {
safe_call("equo i --bdeps @packages_deps @equo_install")
if ( @packages_deps > 0 or @equo_install > 0 );
if ( @packages_deps > 0 or @equo_install > 0 ); ## bail out here, if installs fails. emerge will compile a LOT of stuff
system("equo rm --nodeps @equo_remove") if ( @equo_remove > 0 );
}
}