From owner-freebsd-arch Sun Jul 14 3: 3: 3 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DB1337B400 for ; Sun, 14 Jul 2002 03:03:00 -0700 (PDT) Received: from smtp.netcologne.de (smtp.netcologne.de [194.8.194.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1F6C43E31 for ; Sun, 14 Jul 2002 03:02:58 -0700 (PDT) (envelope-from tmseck-lists@netcologne.de) Received: from localhost (xdsl-195-14-205-193.netcologne.de [195.14.205.193]) by smtp.netcologne.de (8.12.2/8.12.2) with ESMTP id g6EA2tUt029692 for ; Sun, 14 Jul 2002 12:02:55 +0200 (MEST) Received: (qmail 627 invoked by uid 1001); 14 Jul 2002 09:59:39 -0000 Date: Sun, 14 Jul 2002 11:59:39 +0200 From: Thomas Seck To: freebsd-arch@FreeBSD.ORG Subject: Re: Package system flaws? Message-ID: <20020714095939.GA588@laurel.tmseck.homedns.org> Mail-Followup-To: freebsd-arch@FreeBSD.ORG References: <3D27A296.D58FB4B4@softweyr.com> <20020712121427.GD3678@lummux.tchpc.tcd.ie> <20020712144854.GA756@laurel.tmseck.homedns.org> <20020713054141.A26277@misty.eyesbeyond.com> <20020713011750.GA755@laurel.tmseck.homedns.org> <20020714042237.GD931@lizzy.catnook.com> <20020714042623.GB95460@squall.waterspout.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020714042623.GB95460@squall.waterspout.com> User-Agent: Mutt/1.4i Organization: private site in Germany X-PGP-KeyID: DF46EE05 X-PGP-Fingerprint: A38F AE66 6B11 6EB9 5D1A B67D 2444 2FE1 DF46 EE05 X-Attribution: tms Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Will Andrews (will@csociety.org): > The people who do the work should do it the best way they can. > Or, with a volunteer twist, the most enjoyable way they can. Agreed. But portupgrade(1) is somewhat special, because it is the only way you can keep your locally installed packages up to date without thrashing your pkg db. It thus does the work that the pkg_* tools and the ports system should have been doing. People ask regularly why the tools of the sysutils/portupgrade port are not part of the base system. With them being written in anything else than C{,++}, sed, awk or sh this is impossible. Being Joe Random User I suggest the following: - find someone who is willing to re-implement sysutils/portupgrade in a language present in the base system (i.e. _not_ in Perl). Then - fix the dependency handling whithin the pkg_* tools resp. the ports framework. This will make sysutils/portupgrade hopefully obsolete. - After this has been done, start to think about a new flashy package format hich has all the bells and whistles that are missing today. The whole discussion I read so far seems to do the second or even the third step before the first. Just my 2 Euro cents. -- Thomas Seck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message