public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Proposed CVS Cleanup
Date: Sun Feb 18 16:04:01 2001	[thread overview]
Message-ID: <20010218160349.B7240@cvs.gentoo.org> (raw)
In-Reply-To: <20010218174322.A7738@kabbu.akopia.com>; from jerry@thehutt.org on Sun, Feb 18, 2001 at 05:43:22PM -0500

On Sun, Feb 18, 2001 at 05:43:22PM -0500, Jerry A! wrote:
> I'm thinking that this may be a good time to audit the portage tree and
> clean up any cruft.
> 
> Specifically:
> 
> 1. Clean out directories with multiple, older versions of ebuilds.
> 2. Consolidate portages which are replicated in multiple directories.
> 3. Consolidate current-packages and current-packages.new into one file.
> 
> Why now?  Well, since it looks like most of Gentoo is falling into place
> and is growning everyday, now seems like a good time (in my opinion).
> Also, it appears as though with the new portage expansions (xpak) being
> the building blocks for 1.0_rc5, that this going into this with a
> spotless tree may make the work a lot easier.
> 
> Anyway, I'd like to know what you all think.  If it does appear like a
> good idea, then maybe we should get all the committers together, divide
> up the tree and go to town...

I think that's a good idea.  We may want to start discussing how to add a new
feature to portage called "system profiles".  This new feature will allow us to
define a certain "type" of Gentoo Linux system, and then list all the packages
that are part of this system.  Users will be able to select from these various
types at system install time.  For example, a user can decide to install a
"minimal server" set of packages, or a "the drobbins ultimate desktop system"
set.  I plan to record user profile information in /usr/portage/profiles, and
it will allow us to replace the current-packages file with a
/usr/portage/profiles/default file.

Now, some questions.

I still haven't decided how this system will work with the USE variable.  Right
now, optional functionality can be enabled or disabled with USE in make.conf,
so that ebuilds know whether to compile-in optional GNOME support into
particular packages, for example.  Will system profiles include their own 
custom USE settings?  It would seem like they'd have to.  They may also have
other special customization files -- any you can think of?

The USE variable also creates some complications for our .tbz2 binaries that
appear on the CD.  What should the default USE settings be?  I'm thinking that
our binaries could cater to a fully-configured system.  If users want to set
up a minimal system, then can install the sys.tbz2 file, set USE appropriately,
and then compile everything else from sources.

Ideas, questions, comments?

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			



  reply	other threads:[~2001-02-18 23:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-18 15:44 [gentoo-dev] Proposed CVS Cleanup Jerry A!
2001-02-18 16:04 ` drobbins [this message]
2001-02-18 23:17   ` Achim Gottinger

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=20010218160349.B7240@cvs.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-dev@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