问一下emerge的应用

superekcah

有没有什么办法可以在emerge出错时自动跳过，并继续下去的方法，最好还能记录出错的包？
这样像emerge -e system或emerge -w world时就方便多了。
我对脚本不太熟悉

wangtzh

想看出错的包的话,直接看
/var/log/emerge.log(忘了有没有.log了,可以自动补齐) 就行了

Fleta

试试hielvc的emwrap.sh，详见：
http://forums.gentoo.org/viewtopic-t-454345.html?sid=1f4734a05d3cf95e216e7ba1970b9099

sheep204

sorry, post error

Iamthetop

emerge --skipfirst ?

superekcah

Post by Fleta
试试hielvc的emwrap.sh，详见：
http://forums.gentoo.org/viewtopic-t-454345.html?sid=1f4734a05d3cf95e216e7ba1970b9099

emwrap.sh不错，只是觉得里面说的步骤太多了，好像总的要编译整个系统好几次了。

Fleta

Post by superekcah
emwrap.sh不错，只是觉得里面说的步骤太多了，好像总的要编译整个系统好几次了。

不会啦，有很多参数可以用的，远行时如果不加任何参数，会出现Help：

1. # /path/to/emwrap.sh
   
2. 
   
3.       emwrap.sh  v. 4.0.1 "cats is rats mit fuzzy tails"
   
4.       A wrapper for emerge so you can control toolchain updates!
   
5. 
   
6. Usage: emwrap.sh [OPTION]
   
7. 
   
8. Date 4-23-05
   
9. Use at yee own risk. It works for me, but then I wrote it.
   
10. This wrapper can do 3 things for you:
    
11. 1. Test if there is a toolchain, TC, update in "emerge system/world -uD".
    
12. 2. If there is and you want to, then you can rebuild all or part of your TC and then
    
13.    using an edited list to build the other items scheduled to be updated.
    
14. 3. Do the update without updating the TC, toolchain.
    
15. Options:
    
16.    These first flags are the same as what you use with emerge [options] See "man emerge"
    
17.    -h, help   Display this help (default)
    
18.    -f   Fetchs files only
    
19.    -u   update
    
20.    -D   deep
    
21.    -e   Does an  emerge "--emptytree" world/sytem
    
22.    -p   Just like pretend in emerge. Works with all other flags.
    
23.    -N   Tells emerge to include installed packages that are affected by the new USE flags
    
24.    that have changed since the program was built.
    
25.    -B/b build packages only or build them as you emerge packages
    
26.    resume, -r    Continues emwrap from where it stoped. To use rerun the same command
    
27.    and add "r" DONT USE EMWRAP.SH FOR ANYTHING ELSE UNTIL YOU RUN THE -r
    
28.    and emwrap will start from where it stopped without haveing to rebuild everything
    
29.    already done.
    
30.    -K/k   use packages. For use if you have --buildpkg in your /etc/make.conf  or use -B/b
    
31.    -G/g use packages from a  PORTAGE_BINHOST server.
    
32.    system, -s   "-s" is short for system.The same as "emerge system"
    
33.    world, -w    "-w" is short for world. The same as "emerge world"
    
34. 
    
35. For use by the script
    
36.    -t      Rebuilds the toolchain componets only
    
37.    -b      Rebuilds the toolchain and resumeinues the emerge.
    
38.    -1      For use with "t" or "b" only builds the TC once.
    
39.    -S      This is short for a "emerge system --emptytree" build.
    
40.    -W      builds the world files, "emerge world -e", BUT minus the system files.
    
41.    failed     builds the files in the failed list.
    
42.    nc      Turns off color in the script. You still get color in emerge out put.
    
43. 
    
44. The flags are chainable and change whether your doing a system or world emerge and
    
45. from -uD, -N, to -e. There is also a pretend mode, -p. Like emerge -p it
    
46. shows you what will be emerged. I recomemnd that instead of boldy going forth, add
    
47. the -p to the end of the switchs first, to see whats going to be emerged. Then you
    
48. can remove it.
    
49. 
    
50. [color="Red"]Example emwrap.sh -sep ==> emerge system --emptytree -pretend. If you remove the
    
51.    -p it    will do a build of all packages in system except for the TC.
    
52.    NOTE -se or -S do the same thing
    
53. emwrap.sh -set or -wet ==> updates the entire TC.  If the -b switch is used instead
    
54.    of -t then the entire TC is built and then all system/world packages minus
    
55.    toolchain files.
    
56. 
    
57. Examples
    
58.    emwrap.sh  prints help.
    
59.    emwrap.sh -wuDbp Checks for updates to the TC and in the world.
    
60.    emwrap.sh -wuDt==>  emerge world -uD and only does TC update if any.
    
61.    emwrap.sh -wuDb==> updates, if any, the TC and then the world files.
    
62.    emwrap.sh -f{other flags} will fetch the files for you.
    
63.    emwrap.sh system -uDN==> emerge system -uDN, update deep newuse
    
64.    emwrap.sh -Sb1==> emerge system -e build TC once and then system files
    
65. 
    
66. emwrap.sh can "emerge system -e" with or without the TC and remove all packages
    
67.    built during the system emerge for a following "emerge world -e". This is a major
    
68.    time savings as 130+ packages wont be rebuilt during the world half.
    
69.    NOTE -d -c -r have been changed. -d is now -S, -W takes on the old
    
70.    role of -r.-r is now resume and -c has been removed.
    
71.    emwrap.sh -Sb ,builds TC and sytem -e. When it completes run
    
72.    emwrap.sh -W ,this picks where -Sb stoped and builds the rest of
    
73.    the files in the " world -e ". Why use this, well if you want to break an
    
74.    " emerge world -e " up into 2 chunks for two different nights this will do it.[/color]
    
75. 
    
76. Here are the TC build list used in this wraper when doing updates. The first 3 are
    
77.    double builds.
    
78.    If linux-headers   TC="linux-headers glibc $tc_conf binutils gcc glibc binutils gcc"
    
79.    If glibc      TC_glb="glibc $tc_conf binutils gcc glibc binutils gcc"
    
80.    If binutils or gcc   TCmini="$tc_conf binutils gcc binutils gcc"
    
81. These are the single build TC list
    
82.    If linux-headers   TC1="linux-headers glibc $tc_conf binutils gcc "
    
83.    If glibc      TC_glb1="glibc $tc_conf binutils gcc "
    
84.    If binutils or gcc   TCmini1="$tc_conf binutils gcc"
    
85. 
    
86. The TC build sripts are basicly fall through. If you have a linux-headers update
    
87.    then the srcipt will use TC, if its a glibc update then TC_glib and
    
88.    if binutils and/or gcc then TCmini. To force a full TC build use -set, -St or
    
89.    -wet or -seb, -Sb or -web.
    

复制代码

superekcah

我的意思是说他在那个版上讨论的更新整个系统的步骤

gcc-config -l    # make sure of gcc before beginning
emwrap.sh -set or -St
gcc-config -l                 #select the new gcc
emwrap.sh -seb  or -Sb  # We rebuild the TC and then the rest of the system
emwrap.sh -se  or -S      # doing the 2nd system emerge minus the TC
emwrap.sh -set or  -wet   # rebuilds TC against clean system
emwrap.sh -W       # first build of the world files against clean TC system
emwrap.sh -W       # second world rebuild and done

Fleta

讨论归讨论，使用上不受影响，如emwrap.sh -Sb1 = emerge -e systyem;
emwrap.sh -W = emerge -e world-system （或emwrap.sh -Sb1 && emwrap.sh -W = emerge -e world) 等，看你怎么用了。