| 1 |
Dnia 2015-07-30, o godz. 10:57:46 |
| 2 |
William Hubbs <williamh@g.o> napisał(a): |
| 3 |
|
| 4 |
> All, |
| 5 |
> |
| 6 |
> I'm finding in working on Go ebuilds, that we are propegating a |
| 7 |
> src_unpack function that is very similar to the one in vcs-snapshot. |
| 8 |
> |
| 9 |
> This patch adds an EXTRACT_PATH variable to the vcs-snapshot eclass |
| 10 |
> which, if set, puts the extracted archives in the specified directory under ${S}. |
| 11 |
> |
| 12 |
> If it is not set, nothing should happen. |
| 13 |
> |
| 14 |
> This could be used by other types of ebuilds later, but for now it would |
| 15 |
> be used by Go ebuilds. |
| 16 |
> |
| 17 |
> Thoughts? |
| 18 |
|
| 19 |
I'm against it. This doubles the eclass code, adding completely |
| 20 |
orthogonal and incompatible behavior. |
| 21 |
|
| 22 |
The goal of this eclass is to provide a relatively simple way of |
| 23 |
extracting VCS snapshots and putting them in a predictable locations, |
| 24 |
not fitting some random src_unpack() you happen to use. |
| 25 |
|
| 26 |
-- |
| 27 |
Best regards, |
| 28 |
Michał Górny |
| 29 |
<http://dev.gentoo.org/~mgorny/> |
Archives