sabayon / community-buildspec Goto Github PK

if CACHE_VERSION=1 in build.sh, it gets written to a file in vagrant box.
When build.sh is run it compares the CACHE_VERSION to the file; if they don't match (or more specifically if build.yaml is greater than the file), clean cache, update file, continue so if I say remove a while load of packages from my build.sh command, I can bump the version number and ensure on the next run everything is cleaned up. I don't then have to wait for nightly job and make a second change (I'll forget/be lazy

Automatic disable and notification of repositories that contains unsecure and dangerous packages.

New Environment variable available in build.sh to control automatization of the deletion of old versions of packages

KEEP_PREVIOUS_VERSIONS=3 # keep 3 of them

KEEP_PREVIOUS_VERSIONS=-1 # keep them

KEEP_PREVIOUS_VERSIONS=0 # delete old always

REMOTE_OVERLAY should pump PORTDIR instead of using /usr/local/portage, accepting an array of git repositories that would be automatically fetched.

While the method works, https://github.com/Sabayon/community-buildspec/blob/master/scripts/functions.sh#L119 sounds still weak to me. gzip crc is 32bit and is enough for most of packages out there, but this feels still a hack.

Previous attempt to truncate tbz2's xpak data failed, also if the tbz2 where truncated correctly the md5sum of the tbz2 between different builds still was differing.

Instead, it is better to check if the packages have been already installed in the system, as we already do for equery

more verbosing on log would be nice and add for example: date, timings, statistics with genlop and the version of devkit running on the builder too.