Gentoo Archives: gentoo-portage-dev

From: Joakim Tjernlund <joakim.tjernlund@×××××××××.se>
To: "gentoo-portage-dev@l.g.o" <gentoo-portage-dev@l.g.o>
Subject: Re: [gentoo-portage-dev] running ebuild in src tree
Date: Wed, 11 Mar 2015 19:08:05
Message-Id: 1426100880.31989.59.camel@transmode.se
In Reply to: Re: [gentoo-portage-dev] running ebuild in src tree by Zac Medico
1 On Wed, 2015-03-11 at 12:03 -0700, Zac Medico wrote:
2 > On 03/11/2015 11:56 AM, Joakim Tjernlund wrote:
3 > > On Wed, 2015-03-11 at 11:34 -0700, Zac Medico wrote:
4 > > > On 03/11/2015 09:03 AM, Joakim Tjernlund wrote:
5 > > > > When developing code it would be really nice if one could run your ebuild
6 > > > > on that src tree as is(no fetch, unpack etc.)
7 > > >
8 > > > The existing convention is to create an ebuild with version 9999 and use one of the live vcs eclasses
9 > > > such
10 > > > as git-r3 to pull the live sources in the src_unpack function. In a future EAPI, we plan to add some
11 > > > features related to this [1].
12 > >
13 > > I think you misunderstand, [1] is not what I want to do(I think):
14 > >
15 > > Got my src working copy and made a few modds, not commitet yet. Now I just want build/test etc. before
16 > > committing and to do that I just run mytree/overlay/dev-util/myapp/myapp.ebuild compile and voila, my
17 > > code is
18 > > built which I already have in mytree.
19 >
20 > Well, you can create a -9999 ebuild that copies your sources from $directory to $WORKDIR. Maybe use an
21 > environment to configure whether it pulls from a local directory or a vcs repository.
22
23 No copy, just use the current sources. I realize this is not supported ATM but I think
24 it would be a very useful extension. It could just be an extra option or two to ebuild
25
26 Jocke

Replies

Subject Author
Re: [gentoo-portage-dev] running ebuild in src tree Zac Medico <zmedico@g.o>