| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Jason Cipriani wrote: |
| 5 |
> If package A depends on package B, it is reasonable to fail and not |
| 6 |
> build package A if package B fails. However, I am 99% sure that the |
| 7 |
> remaining 171 packages I had to update did not depend on cups (to use |
| 8 |
> that example). It is not reasonable for emerge to fail to update things |
| 9 |
> like gcc and ati-drivers if cups fails. It is also not reasonable to |
| 10 |
> stop emerge for a reason like "another package may use avahi and that's |
| 11 |
> the one you need to fix" -- as in that case a simple emerge -N would |
| 12 |
> take care of the minimal set of packages effected by that change. |
| 13 |
> |
| 14 |
> What I would like to see is a command line option to emerge that enables |
| 15 |
> the following simple behavior: |
| 16 |
> |
| 17 |
> - If package A fails to build, display the error and move package A |
| 18 |
> and all packages that depend on it to the *end* of the update queue, but |
| 19 |
> do not exit. |
| 20 |
> - If a package fails to build for the second time (i.e. it's already |
| 21 |
> been tried and moved), *then* display error and exit as normal. |
| 22 |
|
| 23 |
In portage-2.1.5.3 there are some changes to the --skipfirst |
| 24 |
behavior that are helpful for situations like this. For example, you |
| 25 |
can do something like this: |
| 26 |
|
| 27 |
emerge --update --deep world ; while [ $? != 0 ] ; do emerge |
| 28 |
- --resume --skipfirst ; done |
| 29 |
|
| 30 |
With the new --skipfirst behavior, any packages with unsatisfied |
| 31 |
dependencies will be automatically dropped. You can also mask |
| 32 |
packages via package.mask and --skipfirst will automatically drop |
| 33 |
them too. |
| 34 |
|
| 35 |
Now that this new --skipfirst behavior is implemented as described |
| 36 |
above, it should be relatively easy to adapt the code to implement |
| 37 |
similar a option the makes emerge continue automatically after a |
| 38 |
build failure (as suggested by you and in bug #12768). |
| 39 |
|
| 40 |
Zac |
| 41 |
|
| 42 |
|
| 43 |
-----BEGIN PGP SIGNATURE----- |
| 44 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 45 |
|
| 46 |
iEYEARECAAYFAkhK51gACgkQ/ejvha5XGaP+zQCfRtjPWwaG/0/INhPdkX2Qg7O4 |
| 47 |
8J8An1d/iHN47gBknJ5cLCLozB49Ajjj |
| 48 |
=A7Hj |
| 49 |
-----END PGP SIGNATURE----- |
| 50 |
-- |
| 51 |
gentoo-portage-dev@l.g.o mailing list |
Archives