| 1 |
There's probably not much reason why a filtered set of OPTS can't be |
| 2 |
accepted. I haven't looked this over yet but this code should probably |
| 3 |
handle the filtering: |
| 4 |
|
| 5 |
http://overlays.gentoo.org/proj/python/changeset/171 |
| 6 |
|
| 7 |
from: https://bugs.gentoo.org/show_bug.cgi?id=282474#c4 |
| 8 |
|
| 9 |
-Doug |
| 10 |
|
| 11 |
On Wed, Oct 21, 2009 at 6:03 PM, Zac Medico <zmedico@g.o> wrote: |
| 12 |
|
| 13 |
> Arthur D. wrote: |
| 14 |
> > To Zac: |
| 15 |
> >> I'd suggest passing the -p option to revdep-rebuild on the command |
| 16 |
> >> line. That's how I always do it. Then you can run it again and it's |
| 17 |
> >> supposed to cache the result (if you don't use the -i option). |
| 18 |
> > I know how to pass options on command line. I was asking about changing |
| 19 |
> > default behaviour to respect emerge default options out-of-box. Passing |
| 20 |
> > same options every time is not a good way of doing things, no? |
| 21 |
> |
| 22 |
> Yeah, I think your right. I suppose that revdep-rebuild could simply |
| 23 |
> assume that the default options are good and allow the user to |
| 24 |
> specify --ignore-default-opts if necessary. The only options that I |
| 25 |
> think would conflict are --update, --selective, and --noreplace. |
| 26 |
> -- |
| 27 |
> Thanks, |
| 28 |
> Zac |
| 29 |
> |
| 30 |
> |
Archives