rework of build.sh about gluon-site-ffhb HOT 3 CLOSED

Nothing else. The release name is automatically determined from the last tag in the site repo if none is given, and the build.sh should use that.

Furthermore, with the switch to LEDE, make clean shouldn't be needed anymore before every new version build. So basically, the build.sh would then be

make update
for target in ...; do
  make -j $proc_num GLUON_TARGET="$target" GLUON_BRANCH=stable
done
make manifest GLUON_BRANCH=stable GLUON_PRIORITY=7
make manifest GLUON_BRANCH=testing GLUON_PRIORITY=0

# other stuff that is done in the current build.sh at the end

from gluon-site-ffhb.

make manifest GLUON_BRANCH=stable GLUON_PRIORITY=7

Is it possible to set the date of the stable.manifest to 2/3 weeks in the future? As this would normally be the release date for the stable?

# other stuff that is done in the current build.sh at the end

Does this include the feature to continue a build (statefile) and the determination of the number of processors?

from gluon-site-ffhb.

Nope, using a future date isn't possible. gluon/scripts/rfc3339date.lua is used to generate the date, which always uses the current date. Maybe we should not generate a stable manifest at all?

And the determination of the number of threads to use has to happen before, and I assumed that to remain as indicated by the usage of $proc_num. My snippet wasn't supposed to be the whole new script, only the main commands.

The statefile stuff is obsolete if we no longer execute make clean.

from gluon-site-ffhb.