| 1 |
On Wed, 2015-03-11 at 11:34 -0700, Zac Medico wrote: |
| 2 |
> On 03/11/2015 09:03 AM, Joakim Tjernlund wrote: |
| 3 |
> > When developing code it would be really nice if one could run your ebuild |
| 4 |
> > on that src tree as is(no fetch, unpack etc.) |
| 5 |
> |
| 6 |
> The existing convention is to create an ebuild with version 9999 and use one of the live vcs eclasses such |
| 7 |
> as git-r3 to pull the live sources in the src_unpack function. In a future EAPI, we plan to add some |
| 8 |
> features related to this [1]. |
| 9 |
|
| 10 |
I think you misunderstand, [1] is not what I want to do(I think): |
| 11 |
|
| 12 |
Got my src working copy and made a few modds, not commitet yet. |
| 13 |
Now I just want build/test etc. before committing and to do that I just |
| 14 |
run mytree/overlay/dev-util/myapp/myapp.ebuild compile and voila, my code is |
| 15 |
built which I already have in mytree. |
| 16 |
|
| 17 |
> |
| 18 |
> > Then one can compile, install, build a binary pkg etc. just for test. That way you shorten your |
| 19 |
> > development/test cycle, get to |
| 20 |
> > partially test your brand new ebuild, don't have write |
| 21 |
> > custom build scripts etc. |
| 22 |
> > |
| 23 |
> > Any thoughts on this? |
| 24 |
> > |
| 25 |
> > Jocke |
| 26 |
> > |
| 27 |
> |
| 28 |
> [1] https://bugs.gentoo.org/show_bug.cgi?id=182028 |
Archives