public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kaarthik Sivakumar <kaarthik@clovissolutions.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Sources for the entire OS
Date: Thu, 07 Apr 2005 18:09:02 -0700	[thread overview]
Message-ID: <4255D9AE.80208@clovissolutions.com> (raw)
In-Reply-To: <20050408004841.GF882@butchest.cubesearch.com>

Peter Johanson wrote:
> On Thu, Apr 07, 2005 at 05:42:30PM -0700, Kaarthik Sivakumar wrote:
> 
>>Hi
>>
>>I am not sure if this is the right list. -dev is for developers in
>>general or just developers working ON gentoo? If this is the wrong list
>>please point me to the right one. Thanks.
>>
>>Is there a way to get the entire sources for all of the base OS, not
>>just the kernel? Like in the BSDs, where under /usr/src you have the
>>entire source for the entire OS that you can build and install and you
>>will have a full OS. On my gentoo box, under /usr/src I only have the
>>linux kernel sources. Thanks.
> 
> 
> you can get the source *tarballs* placed into /usr/portage/distfiles by
> doing something like "emerge -e world -f".

But that would give me the source tarballs for *all* the packages. I
guess I just want sources for stuff like glibc, utils like find, grep,
etc which tend to form the base OS. I could do that on a per-package
basis, like 'emerge glibc -f', etc but I was hoping for a meta-port (I
am not sure what it is called here) that has all of this. (I am still
learning how to use portage and its various utilities; I am a gentoo
user since about 4 days now, coming from FreeBSD).

kaarthik
--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-04-08  1:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08  0:42 [gentoo-dev] Sources for the entire OS Kaarthik Sivakumar
2005-04-08  0:48 ` Peter Johanson
2005-04-08  1:04   ` Tom Martin
2005-04-08  1:10     ` Kaarthik Sivakumar
2005-04-08  1:09   ` Kaarthik Sivakumar [this message]
2005-04-08  1:13     ` Mike Frysinger
2005-04-08  1:30     ` Marius Mauch

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=4255D9AE.80208@clovissolutions.com \
    --to=kaarthik@clovissolutions.com \
    --cc=gentoo-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