slitaz-dev-tools rev 87

tazdev: prepa so it will handle flavors creation before syncing mirror (no sense to rebuilt them with a bb)
author Christophe Lincoln <pankso@slitaz.org>
date Sat May 07 06:10:36 2011 +0200 (2011-05-07)
parents 0ed022c04111
children f5b9af99dcb8
files tazdev/tazdev
line diff
     1.1 --- a/tazdev/tazdev	Sat May 07 01:01:27 2011 +0200
     1.2 +++ b/tazdev/tazdev	Sat May 07 06:10:36 2011 +0200
     1.3 @@ -36,6 +36,7 @@
     1.4   dry-push|-dp        Show what will be uploaded to the mirror. Does nothing
     1.5   pull                Download new packages from the main mirror.
     1.6   dry-pull            Show what will be downloaded from the mirror. Does nothing
     1.7 + pack-flavors        Pack all SliTaz Live flavors at once.
     1.8   relpkg|-rp          Archive and upload new package/project version
     1.9   reliso|-ri          Create all main flavors (not loram)\n"
    1.10  }
    1.11 @@ -313,6 +314,21 @@
    1.12  		get_version $@
    1.13  		purge_packages $1
    1.14  		purge_sources $1 ;;
    1.15 +	pack-flavors)
    1.16 +		# Create all flavors files at once. Do we realy need code to monitor
    1.17 +		# flavors changes ? Let just build them all before syncing the mirror.
    1.18 +		get_version $@
    1.19 +		flavors=$slitaz/flavors
    1.20 +		cd $flavors && hg pull -u && cd ..
    1.21 +		for i in *
    1.22 +		do
    1.23 +			echo "Flavor: $i"
    1.24 +			#tazlito pack-flavor $i
    1.25 +			#mv $i.flavor $PKGS
    1.26 +		done
    1.27 +		# FIXME
    1.28 +		echo "FIXME: tazlito will use the host packages list for version"
    1.29 +		echo "FIXME: tazlito must use: $slitaz/packages" ;;
    1.30  	relpkg|-rp)
    1.31  		# Release a slitaz sub-project and upload tarball to mirror
    1.32  		[ -z "$MIRROR_SOURCES" ] && MIRROR_SOURCES="/var/www/slitaz/mirror/sources"