From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge source code but don't build?
Date: Tue, 10 Aug 2010 10:24:50 -0700 [thread overview]
Message-ID: <AANLkTimXRWccvpE+hYKNd+ObuVH6rLYgjCYjReyJrSbb@mail.gmail.com> (raw)
In-Reply-To: <201008101853.13386.wonko@wonkology.org>
On Tue, Aug 10, 2010 at 9:53 AM, Alex Schuster <wonko@wonkology.org> wrote:
> Mark Knecht writes:
>
>> Is there an option in emerge to download and create the source code
>> tree for an application, but then stop at that point, don't build the
>> app and leave the source code tree in place so that I can look at it?
>
> Probably not. But you can use the ebuild command:
>
> ebuild /path/to/category/package.ebuild unpack
>
> Read the man page, I'm not sure if things like fetching will be done when
> necessary.
>
> Wonko
>
>
Thanks Wonko and you too Neil.
Cheers,
Mark
next prev parent reply other threads:[~2010-08-10 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 16:29 [gentoo-user] emerge source code but don't build? Mark Knecht
2010-08-10 16:53 ` Alex Schuster
2010-08-10 17:22 ` Neil Bothwick
2010-08-10 20:17 ` Mark Knecht
2010-08-10 17:24 ` Mark Knecht [this message]
2010-08-10 17:56 ` Paul Hartman
2010-08-10 17:07 ` Neil Bothwick
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=AANLkTimXRWccvpE+hYKNd+ObuVH6rLYgjCYjReyJrSbb@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@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