From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=DATE_IN_PAST_12_24,DMARC_NONE, INVALID_DATE,MAILING_LIST_MULTI autolearn=no autolearn_force=no version=4.0.0 Received: from mailgw2.netvision.net.il ([194.90.1.9]) by cvs.gentoo.org with esmtp (Exim 3.30 #1) id 15XQUi-0007qA-00; Thu, 16 Aug 2001 10:59:44 -0600 Received: from desktop.dan.net (ras5-p113.rlz.netvision.net.il [62.0.86.113]) by mailgw2.netvision.net.il (8.9.3/8.9.3) with SMTP id UAA00274; Thu, 16 Aug 2001 20:02:40 +0300 (IDT) Content-Type: text/plain; charset="iso-8859-1" From: Dan Armak To: desktop@cvs.gentoo.org X-Mailer: KMail [version 1.2] References: <01081515245901.00655@desktop.dan.net> <01081520310503.24777@desktop.dan.net> <997924792.368.4.camel@zoidberg> In-Reply-To: <997924792.368.4.camel@zoidberg> Organization: Gentoo Linux Cc: gentoo-dev@cvs.gentoo.org MIME-Version: 1.0 Message-Id: <01081620004401.00653@desktop.dan.net> Content-Transfer-Encoding: 8bit Subject: [gentoo-dev] Practical suggestion on moving kde/gnome packages Sender: gentoo-dev-admin@cvs.gentoo.org Errors-To: gentoo-dev-admin@cvs.gentoo.org X-BeenThere: gentoo-dev@cvs.gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@cvs.gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Thu Aug 16 11:00:02 2001 X-Original-Date: Thu, 16 Aug 2001 20:00:44 +0300 X-Archives-Salt: ec7f9edb-f722-4196-a569-325f3899e005 X-Archives-Hash: 3b10d3cdccc363d039327a12bfb3fd26 Hi all, Intro: Hallski and I are searching for a way to implement moving the kde/gnome packages to their new locations, I've got a script to update /var/db/pkg with the new location. We ned a way to get all users to run it. First practical suggestion: Take all ebuilds involved, i.e. kde, gnome, and everyhting that depends on them. Make them run the script before taking any other action, before the DEPEND statements. (The scripts are sourced, right? Everything outside the functions will run first.) Notes: 1. Test on developers first. Run script only if MAINTAINER=yes. 2. Store setting somewhere that the script has already been run, and don't run it again. On the other hand, the script does nothing if you run it a second time (but it takes half a second of processor time), and it's safer to always run it for a time. 3. When will we remove the script from the ebuilds? 4. When we remove the copies of the ebuilds from the old locations? 5. How will this integrate into the job system, in case the system appears before we stop using the script? (That's a philosophical question not a practical one). Hallski, hope you're reading this - I'll try to catch you later on cvs too. -- Dan Armak Gentoo Linux Developer, Desktop Team Matan, Israel