From: Dan Naumov <jago@telefragged.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] What's up with the "stable" tree of portage ?
Date: 20 Jun 2002 05:13:40 +0300 [thread overview]
Message-ID: <1024539226.14501.8.camel@localhost.localdomain> (raw)
Hey.
It has been rumored for quite some time now that Gentoo will have a
"stable" branch of portage. This is really essential for people wanting
to run Gentoo on a server and desktop users who would take stability
over anything. However, I haven't heard any "official words" on as to
when will Gentoo actually get this stable branch.
Over time (I've now been a Gentoo users for a few months), I've become
more and more annoyed by the breakage that occurs so often in the one
and only tree of Portage. It seems to me that not enough care and
testing goes into it and I realised that unless the stable branch will
happen soon (2-3 months top), I will consider going back to FreeBSD and
apparently, I am not the only one who thinks in a similar fashion.
So what's the problem ? Lack of human resources ? If that's the case, I
would like to volunteer to help with maintaining the stable branch. I
don't have excessive knowledge of Python, but I've contributed a few
ebuilds (so I know the basics of how things work) and I am willing to
spend a lot of time testing the ebuilds.
I hope I didn't sound too offensive or anything.
Sincerely,
--
#-------------------------------------------------------#
| Dan Naumov (aka Jago on IRC) || Otavantie 2, 50670, |
| Otava Folk Highschool || Otava, Finland. |
#-------------------------------------------------------#
| User of Gentoo Linux : http://www.gentoo.org |
#-------------------------------------------------------#
reply other threads:[~2002-06-20 2:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1024539226.14501.8.camel@localhost.localdomain \
--to=jago@telefragged.com \
--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