Archives
Archives
| From: | "Michał Górny" <mgorny@g.o> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Cc: | ferringb@×××××.com | ||
| Subject: | Re: [gentoo-dev] [Future EAPI] src_fetch() phase function to support VCS fetching | ||
| Date: | Thu, 06 Sep 2012 18:50:34 | ||
| Message-Id: | 20120906205024.129765bb@pomiocik.lan | ||
| In Reply to: | Re: [gentoo-dev] [Future EAPI] src_fetch() phase function to support VCS fetching by Brian Harring |
||
| 1 | On Thu, 6 Sep 2012 09:49:13 -0700 |
| 2 | Brian Harring <ferringb@×××××.com> wrote: |
| 3 | |
| 4 | > One additional thought- re: the scenarios where we don't fetch to an |
| 5 | > intermediate location, then transfer that contents into ${WORKDIR}, |
| 6 | > while a better name is needed, something along the lines of |
| 7 | > RESTRICT=fetches-into-workdir comes to mind. |
| 8 | > |
| 9 | > Basically that restriction would be interpretted as "$WORKDIR must be |
| 10 | > setup/preserved from invocation of src_fetch to actual building". |
| 11 | > |
| 12 | > Via that restrict, both scenarios should be addressed in full. |
| 13 | |
| 14 | Does separate src_fetch() provide any benefit in that scenario? |
| 15 | |
| 16 | -- |
| 17 | Best regards, |
| 18 | Michał Górny |
| File name | MIME type |
|---|---|
| signature.asc | application/pgp-signature |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] [Future EAPI] src_fetch() phase function to support VCS fetching | Brian Harring <ferringb@×××××.com> |
| Re: [gentoo-dev] [Future EAPI] src_fetch() phase function to support VCS fetching | "Rick \\\"Zero_Chaos\\\" Farina" <zerochaos@g.o> |