From: Gaarde <gaarde@yahoo.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] making %95 of users happy
Date: Thu, 18 Apr 2002 05:25:34 -0700 (PDT) [thread overview]
Message-ID: <20020418122534.31311.qmail@web13308.mail.yahoo.com> (raw)
I've notice a pattern emerging here. OK... the pattern has existed for a
long time, but with the advent of systems ala portage that allow lusers to
keep their systems up to date with bleeding edge software... and said lusers
lack of knowledge of what they are getting into... said pattern is becoming
visable to people who don't know better.
These same people, in turn, bitch to those who do... wasting our time
reporting 'bugs' that we are already aware of. While most of the time, said
'bugs' are out of our hands.
Examples:
Zope still using python 2.1 instead of 2.2...
xcdroast using an older version of mkisofs...
qt, kde-libs, gnome-libs, etc all using older versions of libpng...
To me this is an issue with dependency calculations. Gentoo will blindly
update a package regardless of what other packages depend on it. This
solution works great for those who want to keep thier systems bleeding edge.
However, some users are willing to make a sacrifice and go for less-bleeding
edge. For those users, before mentioned pattern causes HUGH problems.
The fix? In a word, sacrifice. Give the user a choice. Let the user decide
if they want to shoot themselves in the head by going with BLEEDING edge
(developers), or if they want to shoot themselves in the foot by using a more
cautious dependency calculation algorhythm. (lusers)
example: Upgrading to mkisofs 1.15a21 will break xcdroast
xcdroast needs mkisofs 1.15a20
cdrecord needs mkisofs 1.15a21 (it doesn't but this is an example)
Tell the user of the conflict, and ask them which path they want to choose.
The results: A choice in how anal the dependancy calculations are.
The goal is to ALWAYS keep the system as bleeding-edge as possible, upon user
choice, back off on certain packages to fullfill said dependancies.
At the very least, let the user know where the dependancy issues are!
=====
---
"To thine own self be true." - Shakespeare
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
next reply other threads:[~2002-04-18 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 12:25 Gaarde [this message]
2002-04-18 18:29 ` [gentoo-dev] making %95 of users happy Todd Wright
2002-04-18 19:28 ` Stefan Boresch
2002-04-19 3:25 ` Fuper
2002-04-19 12:04 ` Todd Wright
2002-04-18 22:09 ` Sherman Boyd
2002-04-19 14:15 ` Fuper
2002-04-18 19:35 ` Terje Kvernes
2002-04-19 8:42 ` Paul de Vrieze
2002-04-19 9:44 ` Terje Kvernes
2002-04-19 10:19 ` Einar Karttunen
2002-04-19 11:34 ` Mike Payson
-- strict thread matches above, loose matches on Subject: below --
2002-04-19 17:57 Gaarde
2002-04-20 0:30 ` John White
2002-04-20 18:26 Gaarde
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=20020418122534.31311.qmail@web13308.mail.yahoo.com \
--to=gaarde@yahoo.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