From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: "gentoo-portage-dev@lists.gentoo.org"
<gentoo-portage-dev@lists.gentoo.org>
Subject: Re: [gentoo-portage-dev] Re: running ebuild in src tree
Date: Fri, 13 Mar 2015 08:13:01 +0000 [thread overview]
Message-ID: <1426234381.3123.16.camel@transmode.se> (raw)
In-Reply-To: <pan$6adfb$63967047$f1fe9949$f8e410f6@cox.net>
On Fri, 2015-03-13 at 06:32 +0000, Duncan wrote:
> Joakim Tjernlund posted on Thu, 12 Mar 2015 17:26:59 +0000 as excerpted:
>
> > No, there can be no copy of sources for what I want. It just gets in the way having to do that.
>
> ??
>
> Copying to tmpfs is copying to memory, and copying to memory in /some/ form must occur in ordered to
> operate on the files at all, that is, with any build at all, so I don't see the problem, at least if
> you're
> working on a machine with say 2+ gigs RAM. (There might be problems on a
> half-gig RAM machine, but that's not particularly appropriate as a developer machine in any case, these
> days, unless you're talking embedded, which you didn't mention.)
>
> But of course, gentoo/portage lets you do it your way too, as demonstrated by the hacks you posted. =:^)
>
When you are developing SW you do the edit/build cycle often and it is really
annoying to copy a big src tree, rebuild everything (as timestamps, deps changes), move to another
src to do any debugging etc. Try it on your own development by just copying you src tree every time
you want to build, you get very tired of it real soon :)
Don't get me wrong, portage is a wounderful pkg mgr, I just want to extend its use to be more
helpful during development too, without having to do really ugly hacks like I showed you.
Jocke
next prev parent reply other threads:[~2015-03-13 8:13 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
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 [this message]
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=1426234381.3123.16.camel@transmode.se \
--to=joakim.tjernlund@transmode.se \
--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