cookutils rev 243
cook, docs: tiny edits
author | Paul Issott <paul@slitaz.org> |
---|---|
date | Fri May 27 19:18:56 2011 +0100 (2011-05-27) |
parents | 12f01fb089b8 |
children | e35efad312d1 |
files | cook doc/cookutils.en.html |
line diff
1.1 --- a/cook Fri May 27 18:46:06 2011 +0200 1.2 +++ b/cook Fri May 27 19:18:56 2011 +0100 1.3 @@ -174,7 +174,7 @@ 1.4 install=$WOK/$WANTED/install 1.5 wanted_stuff=$WOK/$WANTED/stuff 1.6 fi 1.7 - # Kernel version is set from linux-api-headers since it part of toolchain. 1.8 + # Kernel version is set from linux-api-headers since it is part of toolchain. 1.9 if [ -f "$INSTALLED/linux-api-headers/receipt" ]; then 1.10 kvers=$(grep ^VERSION= $INSTALLED/linux-api-headers/receipt | cut -d '"' -f 2) 1.11 fi 1.12 @@ -866,7 +866,7 @@ 1.13 pkgdb) 1.14 # Create suitable packages list for TazPKG and only for built packages 1.15 # as well as flavors files for TazLiTo. We dont need logs since we do it 1.16 - # manualy to ensure everything is fine before syncing the mirror. 1.17 + # manually to ensure everything is fine before syncing the mirror. 1.18 case "$2" in 1.19 --flavors) 1.20 continue ;; 1.21 @@ -943,8 +943,8 @@ 1.22 time=$(($(date +%s) - $time)) 1.23 echo -e "Packages: $nb - Time: ${time}s\n" 1.24 1.25 - # Create all flavors files at once. Do we realy need code to monitor 1.26 - # flavors changes ? Let just build them with packages lists before 1.27 + # Create all flavors files at once. Do we really need code to monitor 1.28 + # flavors changes ? Lets just build them with packages lists before 1.29 # syncing the mirror. 1.30 [ "$2" == "--flavors" ] || exit 1 1.31 [ ! -d "$flavors" ] && echo -e "Missing flavors: $flavors\n" && exit 1
2.1 --- a/doc/cookutils.en.html Fri May 27 18:46:06 2011 +0200 2.2 +++ b/doc/cookutils.en.html Fri May 27 19:18:56 2011 +0100 2.3 @@ -180,8 +180,8 @@ 2.4 $ cook list-wok 2.5 </pre> 2.6 <p> 2.7 - When creatin packages DB, cook will check if you have a flavors repo in 2.8 - /home/slitaz/flavors, if so, it will pack all flavor using the latest 2.9 + When creating the packages DB, cook will check if you have a flavors repo in 2.10 + /home/slitaz/flavors, if so, it will pack all flavors using the latest 2.11 packages list available. To create a packages list and the Live flavors 2.12 files: 2.13 </p>