From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DMARC_MISSING, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from acme.geekasylum.org (acme.geekasylum.org [203.30.145.10]) by chiba.3jane.net (Postfix) with ESMTP id 707F9AC38F for ; Thu, 18 Apr 2002 13:29:54 -0500 (CDT) Received: from buffy (buffy.geekasylum.org [203.30.145.20]) by acme.geekasylum.org (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with SMTP id g3IITr427292 for ; Fri, 19 Apr 2002 04:29:53 +1000 From: "Todd Wright" To: Subject: RE: [gentoo-dev] making %95 of users happy Date: Fri, 19 Apr 2002 04:29:52 +1000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <20020418122534.31311.qmail@web13308.mail.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: bae53a5d-b439-4d14-a2ca-bded49ad1fb7 X-Archives-Hash: e46af1515eb81d74014cfdce086215ab Gaarde wrote: > Examples: > Zope still using python 2.1 instead of 2.2... > xcdroast using an older version of mkisofs...=20 > qt, kde-libs, gnome-libs, etc all using older versions of libpng... >=20 > 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=20 > bleeding edge.=20 > However, some users are willing to make a sacrifice and go for=20 > less-bleeding > edge. For those users, before mentioned pattern causes HUGH problems. >=20 > The fix? In a word, sacrifice. Give the user a choice. Let the=20 > user decide > example: Upgrading to mkisofs 1.15a21 will break xcdroast >=20 > xcdroast needs mkisofs 1.15a20 > cdrecord needs mkisofs 1.15a21 (it doesn't but this is an example) This is exactly what I am concerned about, and why I posted about = "Tagging releases" - and presumably what started the "Gentoo Branches" = thread. The example may not be good, but the idea holds. Regardless of if you like branches or not, there needs to be a way to = lock a collective group of packages at a particular level where they all = co-exist nicely. This is normally known as a "stable" release. The = best and worst thing about Gentoo is that it is constantly changing - = new ebuilds appearing all the time. I emerge rsync to update my portage = tree in the hope of finding a fix to a broken ebuild that I want, and = suddenly Im faced with new versions of things I already nailed down. Using the =3Dcategory/package parameters isnt good enough. Often 2 = versions of a library wont co-exist (out of the box) - one may overwrite = another, but a new ebuild for package x might require the new library, = while another package requires the old. Someone in the development team needs to seriously think about this = problem. And to the person (Andrew I think) who quoted the following from the = gentoo site as a reason for not having release branches... "*Portage allows you to set up Gentoo Linux the way you like it*..." It doesnt. Just when I get it how I like it, it changes. -- _--_|\ --------- Todd Wright -- wylie@geekasylum.org -------- / \ =20 \_.--._* <--- http://www.dreams.darker.net/~wylie/ v Mobile: +61-403-796-001 Ph: +61-2-9521-8677 ----------------------------------------------------------------