1 |
On Friday, December 6, 2019 3:44:38 PM PST Sergei Trofimovich wrote: |
2 |
> On Fri, 6 Dec 2019 12:09:31 -0800 |
3 |
> |
4 |
> Georgy Yakovlev <gyakovlev@g.o> wrote: |
5 |
> > Default output just prints crate name. |
6 |
> > With -vv we can see all cargo options and rustc args. |
7 |
> > |
8 |
> > Signed-off-by: Georgy Yakovlev <gyakovlev@g.o> |
9 |
> > --- |
10 |
> |
11 |
> Looks good! |
12 |
> |
13 |
> I had to do an equivalent locally at least a few times. |
14 |
Pushed! |
15 |
> |
16 |
> While at it I also suggest adding equivalent of |
17 |
> econf's/emake's ${EXTRA_ECONF} and ${EXTRA_EMAKE} |
18 |
> to allow users to inject arbitrary stuff. For example |
19 |
> to sneak in '-Z' options globally. |
20 |
> |
21 |
> Say, ${CARGO_BUILD_EXTRA}, ${CARGO_INSTALL_EXTRA}, |
22 |
> ${CARGO_TEST_EXTRA}. |
23 |
> |
24 |
|
25 |
Yeah, it's on my to-do list for this eclass. |
26 |
1 question tho, should it come after "$@" or before? Do you use it? |
27 |
I know cargo can be picky about order and some ebuilds rely on passing params |
28 |
in phase funcs. |