Re: [gentoo-portage-dev] running ebuild in src tree

[Zac Medico]

On 03/11/2015 12:08 PM, Joakim Tjernlund wrote:
> On Wed, 2015-03-11 at 12:03 -0700, Zac Medico wrote:
>> On 03/11/2015 11:56 AM, Joakim Tjernlund wrote:
>>> On Wed, 2015-03-11 at 11:34 -0700, Zac Medico wrote:
>>>> On 03/11/2015 09:03 AM, Joakim Tjernlund wrote:
>>>>> When developing code it would be really nice if one could run your ebuild
>>>>> on that src tree as is(no fetch, unpack etc.)
>>>>
>>>> The existing convention is to create an ebuild with version 9999 and use one of the live vcs eclasses
>>>> such
>>>> as git-r3 to pull the live sources in the src_unpack function. In a future EAPI, we plan to add some
>>>> features related to this [1].
>>>
>>> I think you misunderstand, [1] is not what I want to do(I think):
>>>
>>> Got my src working copy and made a few modds, not commitet yet. Now I just want build/test etc. before
>>> committing and to do that I just run mytree/overlay/dev-util/myapp/myapp.ebuild compile and voila, my
>>> code is
>>> built which I already have in mytree.
>>
>> Well, you can create a -9999 ebuild that copies your sources from $directory to $WORKDIR. Maybe use an
>> environment to configure whether it pulls from a local directory or a vcs repository.
>
> No copy, just use the current sources. I realize this is not supported ATM but I think
> it would be a very useful extension. It could just be an extra option or two to ebuild

You can already write the code to do this in the ebuild. Maybe have it
create a symlink to your source directory. You can use environment
variables, so there's no need to special options for this. It's really
none of portage's business where your source code comes from.
-- 
Thanks,
Zac