| 1 |
[2019-12-06 16:16:32-0800] Georgy Yakovlev: |
| 2 |
> On Friday, December 6, 2019 3:44:38 PM PST Sergei Trofimovich wrote: |
| 3 |
> > On Fri, 6 Dec 2019 12:09:31 -0800 |
| 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 |
> > While at it I also suggest adding equivalent of |
| 12 |
> > econf's/emake's ${EXTRA_ECONF} and ${EXTRA_EMAKE} |
| 13 |
> > to allow users to inject arbitrary stuff. For example |
| 14 |
> > to sneak in '-Z' options globally. |
| 15 |
> > |
| 16 |
> > Say, ${CARGO_BUILD_EXTRA}, ${CARGO_INSTALL_EXTRA}, |
| 17 |
> > ${CARGO_TEST_EXTRA}. |
| 18 |
> > |
| 19 |
> |
| 20 |
> Yeah, it's on my to-do list for this eclass. |
| 21 |
> 1 question tho, should it come after "$@" or before? Do you use it? |
| 22 |
> I know cargo can be picky about order and some ebuilds rely on passing params |
| 23 |
> in phase funcs. |
| 24 |
|
| 25 |
I think it should go after `cargo {build,install,test}` and before any |
| 26 |
non-option argument, similar to how POSIX getopt(3) behaves (but that GNU |
| 27 |
breaks without setting POSIXLY_CORRECT=1). |
Archives