From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1Hkcqx-0004QP-T0 for garchives@archives.gentoo.org; Sun, 06 May 2007 09:16:28 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l469Ewux001550; Sun, 6 May 2007 09:14:58 GMT Received: from dd14500.kasserver.com (dd14500.kasserver.com [85.13.135.241]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l469CCDb030259 for ; Sun, 6 May 2007 09:12:12 GMT Received: from hoshino (unknown [82.139.196.236]) by dd14500.kasserver.com (Postfix) with ESMTP id 06DE31432D for ; Sun, 6 May 2007 11:12:12 +0200 (CEST) From: expose@luftgetrock.net To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP 42 news item for review: Radiant upgrade Date: Sun, 6 May 2007 11:11:59 +0200 User-Agent: KMail/1.9.5 References: <1178433936.13701.10.camel@ip6-localhost> In-Reply-To: <1178433936.13701.10.camel@ip6-localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705061111.59728.expose@luftgetrock.net> X-Archives-Salt: 4f0c1ffa-358e-4073-b5b9-e7f42f33637d X-Archives-Hash: 8e32399b69ffebabdc9609fb2d07aeef Hans de Graaff wrote: > Hi, > > I realize that we are in the middle of a huge discussion on GLEP 42 news > items, but I think I have a need for such a news item at the moment, and > getting more items to discuss may help move the discussion forward. I'm > appending the news item below. > > That said, unfortunately GLEP 42 is not going to be useful for the > intended purpose... The reason for this is that it does not take into > account if the specific user can actually upgrade because it does not > take stable/testing into account. So a user on stable will see the > message once the new package hits the tree but can't upgrade yet, and > will probably have forgotten if the package moves to stable after one or > several months. > > What I would like to happen is that the message is added to the tree > once, shown to users who have dev-ruby/radiant in testing immediately, > and only shown to other users of dev-ruby/radiant when they move radiant > to testing or radiant itself becomes stable for them. I don't see a > mechanism to avoid this with the current GLEP, but perhaps I overlooked > something? I guess this is what the Display-If-Upgrading-From-To: that > Ciaran mentioned would do, but I'm wondering if GLEP 42 makes any sense > without it. ++ Considering the news item below, it does clearly show the difference to the paludis item, as it is indeed critical: There seems to be no foolproof method to fix this in a matter of seconds. It fits into the group of new items which you dont even need to read, to know that you will likely need more than a few minutes to work through this and get things back working, just because it is a news item and nothing else. I'd like those items to be the standard, not those which dont even break anything in the first place, and even further can be fixed in a matter of seconds using a foolproof method. Additionally, the wording of the GLEP as far as I know it seems to support this, personal preference to or fro. Corrections welcome. > Title: Radiant upgrade from 0.5.2 to 0.6.* > Author: Hans de Graaff > Content-Type: text/plain > Posted: 06-May-2007 > Revision: 1 > Display-If-Installed: =dev-ruby/radiant-0.5.2 > > Radiant 0.6.* is in many cases not a seamless update from 0.5.2, and > if you are currently running your site based on the gem then the > upgrade will break your site. Apart from a number of minor > configuration changes, the plugin system has been removed and changed > to a new extension system with slightly different semantics. > > If you have any plugins installed in your Radiant installation you > will need to find replacement extensions first or rewrite the plugins > to use the extension system. > > More information about upgrading can be found here: > > http://dev.radiantcms.org/radiant/wiki/HowToUpgrade05xTo06 > > and an overview of the changes including instructions to update > plugins here: > > http://seancribbs.com/tech/2007/04/18/whats-new-in-radiant-0-6/ -- gentoo-dev@gentoo.org mailing list