public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 13:17:00 -0700	[thread overview]
Message-ID: <AANLkTi=PfJkjFOSuz=kiMLaHKP68z8=K6dyMWzcT6EBR@mail.gmail.com> (raw)
In-Reply-To: <20100810182244.2b90471b@zaphod.digimed.co.uk>

On Tue, Aug 10, 2010 at 10:22 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Tue, 10 Aug 2010 18:53:12 +0200, Alex Schuster wrote:
>
>> ebuild /path/to/category/package.ebuild unpack
>>
>> Read the man page, I'm not sure if things like fetching will be done
>> when necessary.
>
> It will, ebuild carries out any prior steps if they are needed. You may
> want to use ebuild ... prepare instead of ebuild ... unpack. It carries
> out any pre-compilation steps, like applying patches.
>
> If you are doing this because you want to apply a patch yourself, you can
> use one of the above, apply your patches, then run ebuild ... merge to
> complete the process and install it. man 1 ebuild explains it all.
>
>
> --
> Neil Bothwick
>
> What do you do when you see an endangered animal eating an endangered
> plant?
>

In my case, due to conversations on another list about a piece of
software that's important to me, it was simply to look at how
copyrights are set up in that program's source code. (I.e. - who's
names are named, what dates, etc.)

Cheers,
Mark



  reply	other threads:[~2010-08-10 21:03 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 [this message]
2010-08-10 17:24   ` Mark Knecht
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='AANLkTi=PfJkjFOSuz=kiMLaHKP68z8=K6dyMWzcT6EBR@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