1 |
On 03/11/2015 11:56 AM, Joakim Tjernlund wrote: |
2 |
> On Wed, 2015-03-11 at 11:34 -0700, Zac Medico wrote: |
3 |
>> On 03/11/2015 09:03 AM, Joakim Tjernlund wrote: |
4 |
>>> When developing code it would be really nice if one could run your ebuild |
5 |
>>> on that src tree as is(no fetch, unpack etc.) |
6 |
>> |
7 |
>> The existing convention is to create an ebuild with version 9999 and use one of the live vcs eclasses such |
8 |
>> as git-r3 to pull the live sources in the src_unpack function. In a future EAPI, we plan to add some |
9 |
>> features related to this [1]. |
10 |
> |
11 |
> I think you misunderstand, [1] is not what I want to do(I think): |
12 |
> |
13 |
> Got my src working copy and made a few modds, not commitet yet. |
14 |
> Now I just want build/test etc. before committing and to do that I just |
15 |
> run mytree/overlay/dev-util/myapp/myapp.ebuild compile and voila, my code is |
16 |
> built which I already have in mytree. |
17 |
|
18 |
Well, you can create a -9999 ebuild that copies your sources from |
19 |
$directory to $WORKDIR. Maybe use an environment to configure whether it |
20 |
pulls from a local directory or a vcs repository. |
21 |
-- |
22 |
Thanks, |
23 |
Zac |