| 1 |
On Tuesday 16 September 2008 20:43:06 Dale wrote: |
| 2 |
> I have used --skipfirst before but I also don't think it is a good |
| 3 |
> idea. For a idiot like me to say that must mean something. I guess it |
| 4 |
> would depend on the package as to whether it could be skipped or not. |
| 5 |
> If I do a emerge -e world, I prefer nothing to fail else what is the point? |
| 6 |
|
| 7 |
Sometimes stuff does fail - you can't fully know beforehand if an ebuild will |
| 8 |
succeed or not. --skipfirst is perfectly safe if you have looked at the |
| 9 |
package list and know that there's no dependency issues. The danger is |
| 10 |
blindly resuming without understanding the consequences. |
| 11 |
|
| 12 |
For example, lets assume there's a package called alan-fonts-meta which |
| 13 |
depends on 20 fancy wingding-type fonts. Lets also assume that I was a dork |
| 14 |
when coding one font ebuild at 4am and botched the SRC_URI. That ebuild will |
| 15 |
fail, but you know for sure that you can safely --resume --skipfirst |
| 16 |
(followed by a scathing email with a blunt instrument as payload). |
| 17 |
|
| 18 |
Other examples exist. OTOH, if the expat upgrade of some months ago failed, a |
| 19 |
blind resume would likely have caused endless troubles. |
| 20 |
|
| 21 |
-- |
| 22 |
alan dot mckinnon at gmail dot com |
Archives