From: davecode@nospammail.net
To: gentoo-releng@lists.gentoo.org
Subject: [gentoo-releng] Free-standing Portage / Recent stage3 tarballs / Beta
Date: Sat, 02 Feb 2008 20:31:09 -0800 [thread overview]
Message-ID: <1202013069.18679.1234757825@webmail.messagingengine.com> (raw)
Hi Gentoo-
My overall impression of Gentoo is "what a fantastic system"! I can't
believe how good, really. These are all fairly minor things. I'm new
to Gentoo, so forgive dumb ignorance, but Linux and programming are my
profession.
For your 2008.0 release:
The 2007.0~ppc branch fails to upgrade over a Bash / Portage block. So
will 2008.0 break too, until attended? A Bash / Portage conflict is the
worst possible.
I tried to fix it (from zsh chroot into Gentoo) but gave up. Stock
advice on FAQs does not work in this thorny case. Forums show
occasional situations between Python / Portage, too.
I do not want/ask your help, but only to share a thought:
Portage should have embedded Python and embedded Bash. Exactly the
versions it needs, with bare minimum required libraries, statically
compiled.
The Portage 'snapshot' is already a special install step. And Gentoo
already ships regular snapshots. The only thing missing is embedding
the dependencies directly.
I've never embedded Bash, but have Python, several times. Bash could
probably work too. The combined ELFs weigh around 2 MB total, not bad
for a critical executive controller like Portage which has its own
dedicated snapshots.
Finally - how about some recent stage3 ~arch tarballs. I can't find
any. Most distros do daily/weekly/monthly build snapshots. The only
snapshots for Gentoo seem to be Portage snapshots. Am I wrong? I know
the 2008.0 beta is due soon, but I mean on a continuous basis. Not
binary builds, just the latest ~arch tarball. If not frequent, at least
quarterly?
Normal ppc 2007.0 works fine from a dependency standpoint. The entire
reason for trying Gentoo is that ppc boxes need the absolute most
bleeding edge of everything. Hence the interest in Gentoo and
specifically ~arch. We also want the latest GNOME anyhow, plus
compiz-fusion.
Would it be best to wait a month until beta, or is it reasonable to
install ~arch right now? A few bugzilla contributions from us might
help the beta project but deadly bash/Portage conflicts are a little too
thick for my taste right now...
Thank you!
--
davecode@nospammail.net
--
http://www.fastmail.fm - A no graphics, no pop-ups email service
--
gentoo-releng@lists.gentoo.org mailing list
next reply other threads:[~2008-02-03 4:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 4:31 davecode [this message]
2008-02-03 5:16 ` [gentoo-releng] Free-standing Portage / Recent stage3 tarballs / Beta Andrew Gaffney
2008-02-03 5:56 ` [gentoo-releng] " davecode
2008-02-03 6:13 ` Chris Gianelloni
2008-02-03 8:37 ` davecode
2008-02-03 8:46 ` Christian Faulhammer
2008-02-03 8:48 ` Rémi Cardona
2008-02-03 12:19 ` Markus Hauschild
2008-02-03 17:16 ` Alex Howells
2008-02-03 18:27 ` M. Edward (Ed) Borasky
2008-02-03 22:44 ` Alex Howells
2008-02-04 4:28 ` M. Edward (Ed) Borasky
2008-02-04 16:42 ` Alex Howells
2008-02-04 17:17 ` Chris Gianelloni
2008-02-05 2:58 ` M. Edward (Ed) Borasky
2008-02-04 5:40 ` [gentoo-releng] " keith
2008-02-05 7:35 ` [gentoo-releng] " davecode
2008-02-05 13:57 ` M. Edward (Ed) Borasky
2008-02-05 14:01 ` Dale
2008-02-05 14:21 ` Alex Howells
2008-02-05 14:29 ` Dale
2008-02-05 16:44 ` Chris Gianelloni
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=1202013069.18679.1234757825@webmail.messagingengine.com \
--to=davecode@nospammail.net \
--cc=gentoo-releng@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