From: Jerry A! <jerry@thehutt.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Proposed CVS Cleanup
Date: Sun Feb 18 15:44:01 2001 [thread overview]
Message-ID: <20010218174322.A7738@kabbu.akopia.com> (raw)
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...
--Jerry
name: Jerry Alexandratos || Open-Source software isn't a
phone: 703.599.6023 || matter of life or death...
email: jerry@thehutt.org || ...It's much more important
|| than that!
next reply other threads:[~2001-02-18 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 15:44 Jerry A! [this message]
2001-02-18 16:04 ` [gentoo-dev] Proposed CVS Cleanup drobbins
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=20010218174322.A7738@kabbu.akopia.com \
--to=jerry@thehutt.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