Skip to content

Commit

Permalink
beesh: join together verify_new_package_variables and extract_new_pac…
Browse files Browse the repository at this point in the history
…kage_variables

we want to expand the handling of variables changed by the beefile a bit
which is easier implement and follow when done in a single function
  • Loading branch information
donald committed Jul 5, 2016
1 parent 4bc583b commit 94ef841
Showing 1 changed file with 1 addition and 4 deletions.
5 changes: 1 addition & 4 deletions src/beesh.sh.in
Original file line number Diff line number Diff line change
Expand Up @@ -732,7 +732,7 @@ function save_current_package_variables() {
oPKGREVISION=${PKGREVISION}
}

function verify_new_package_variables() {
function extract_new_package_variables() {
nPKGFULLNAME="${PKGNAME}${PKGEXTRANAME:+_${PKGEXTRANAME}}"

if [ "${oPKGFULLNAME}" != "${PKGFULLNAME}" ] ; then
Expand Down Expand Up @@ -763,9 +763,7 @@ function verify_new_package_variables() {
fi
fi
PKGFULLVERSION="${PKGVERSION}${PKGEXTRAVERSION:+_${PKGEXTRAVERSION}}"
}

function extract_new_package_variables() {
if [ "${PKGNAME}" != "${oPKGNAME}" ] ; then
# pkgname changed! we allow prefixing 'anything-' to the packagename
if [ "${PKGNAME}" != "${PKGNAME/-${oPKGNAME}}-${oPKGNAME}" ] ; then
Expand Down Expand Up @@ -989,7 +987,6 @@ save_current_package_variables
# now set PKGARCH if set or changed by user via ARCH=.. and not given via file.arch.bee
: ${PKGARCH:=${ARCH}}

verify_new_package_variables
extract_new_package_variables

config_handle_deprecated_beefile
Expand Down

0 comments on commit 94ef841

Please sign in to comment.