public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] running ebuild in src tree
Date: Wed, 11 Mar 2015 11:34:07 -0700	[thread overview]
Message-ID: <55008A9F.1060705@gentoo.org> (raw)
In-Reply-To: <1426089808.31989.42.camel@transmode.se>

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].

> Then one can compile, install, build a binary pkg etc. just for test. That way you shorten your 
> development/test cycle, get to
> partially test your brand new ebuild, don't have write
> custom build scripts etc.
> 
> Any thoughts on this?
> 
>  Jocke 
> 

[1] https://bugs.gentoo.org/show_bug.cgi?id=182028
-- 
Thanks,
Zac


  reply	other threads:[~2015-03-11 18:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 16:03 [gentoo-portage-dev] running ebuild in src tree Joakim Tjernlund
2015-03-11 18:34 ` Zac Medico [this message]
2015-03-11 18:56   ` Joakim Tjernlund
2015-03-11 19:03     ` Zac Medico
2015-03-11 19:08       ` Joakim Tjernlund
2015-03-11 19:19         ` Zac Medico
2015-03-12  1:27       ` [gentoo-portage-dev] " Duncan
2015-03-12 17:26         ` Joakim Tjernlund
2015-03-13  6:32           ` Duncan
2015-03-13  8:13             ` Joakim Tjernlund
2015-03-13 10:58               ` Duncan
2015-03-15  0:52           ` Alec Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55008A9F.1060705@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox