public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kristian Benoit <kbenoit@opersys.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-embedded] Interactive command
Date: Thu, 14 Jul 2005 12:51:34 -0400	[thread overview]
Message-ID: <1121359894.5971.98.camel@localhost> (raw)
In-Reply-To: <42D68C5B.1000005@gentoo.org>

On Thu, 2005-07-14 at 12:01 -0400, Michael Cummings wrote:
> Not sure of the mechanics on how
> this is done for the portage emerge process, but even stopping the
> emerge process for those packages that *must* have a preconfig done
> would help (are there any though? I can think of one maybe, but not
> really anything to demand new functionality in portage yet).

This problem is mostly present in the embedded world. As the packages
have to be fine tuned (as a kernel is) at compiled time for the system
on which it is beiing build. For example, uClibc and busybox uses a
kernel like config.

As described on busybox's home page:

"BusyBox combines tiny versions of many common UNIX utilities into a
single small executable. It provides replacements for most of the
utilities you usually find in GNU fileutils, shellutils, etc. The
utilities in BusyBox generally have fewer options than their
full-featured GNU cousins; however, the options that are included
provide the expected functionality and behave very much like their GNU
counterparts. BusyBox provides a fairly complete environment for any
small or embedded system."

With so many applications/options provided by a single package, that aim
to go in small memory/storage system, one must understand that users
must fine tune it.

Kristian

-- 
gentoo-dev@gentoo.org mailing list



      reply	other threads:[~2005-07-14 16:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 22:44 [gentoo-dev] Interactive command Kristian Benoit
2005-07-13 23:49 ` Donnie Berkholz
2005-07-14 14:45   ` Kristian Benoit
2005-07-14  0:02 ` [gentoo-dev] Re: [gentoo-embedded] " Ned Ludd
2005-07-14  5:13   ` Kristian Benoit
2005-07-14  6:43     ` Patrick Lauer
2005-07-14 14:37       ` Kristian Benoit
2005-07-14 11:58     ` Ned Ludd
2005-07-14 12:37       ` Jason Stubbs
2005-07-14 14:56         ` Kristian Benoit
2005-07-16  9:20           ` Drake Wyrm
2005-08-23 13:41         ` Paul de Vrieze
2005-08-23 15:12           ` Jason Stubbs
2005-08-25 11:23             ` Paul de Vrieze
2005-07-14 14:29       ` Kristian Benoit
2005-07-14 16:01         ` Michael Cummings
2005-07-14 16:51           ` Kristian Benoit [this message]

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=1121359894.5971.98.camel@localhost \
    --to=kbenoit@opersys.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