From owner-freebsd-advocacy@FreeBSD.ORG Wed Sep 17 16:53:11 2003 Return-Path: Delivered-To: freebsd-advocacy@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70DC916A4B3 for ; Wed, 17 Sep 2003 16:53:11 -0700 (PDT) Received: from zeus.acuson.com (ac17860.acuson.com [157.226.71.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4492A43FBF for ; Wed, 17 Sep 2003 16:53:10 -0700 (PDT) (envelope-from DavidJohnson@Siemens.com) Received: from mvaexch02 ([157.226.230.209]:4543 helo=mvaexch02.acuson.com) by zeus.acuson.com with esmtp (Exim 4.14) id 19zm6d-0005hh-4L; Wed, 17 Sep 2003 16:53:07 -0700 Received: by mvaexch02.acuson.com with Internet Mail Service (5.5.2653.19) id ; Wed, 17 Sep 2003 16:50:50 -0700 Received: from dhcp-46-151.acuson.com ([157.226.46.151]) by mvaexch01.acuson.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id SXCQZSH0; Wed, 17 Sep 2003 16:50:00 -0700 From: Johnson David To: Michal Pasternak Organization: Siemens Medical Systems Date: Wed, 17 Sep 2003 16:52:08 -0700 User-Agent: KMail/1.5.3 References: <20030917160654.52ceb56c.kitbsdlist2@HotPOP.com> <200309171548.22742.DavidJohnson@Siemens.com> <20030917230919.GA8428@pasternak.w.lub.pl> In-Reply-To: <20030917230919.GA8428@pasternak.w.lub.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309171652.08667.DavidJohnson@Siemens.com> X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *19zm6d-0005hh-4L*J1V5ScFmfhg* X-SA-Exim-Scanned: No; SAEximRunCond expanded to false cc: freebsd-advocacy@freebsd.org Subject: Re: Desktop FreeBSD X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2003 23:53:11 -0000 On Wednesday 17 September 2003 04:09 pm, Michal Pasternak wrote: > ... even if Debian's way is the one, right way to do that? That would > be a little silly, don't you think? I am really, really interested > how would you solve this problem. I think we need to define exactly what we want to do first. In terms of wm menu configuration, we don't have anything. Debian's way might be the best solution. But in terms of package management, I'll take ports and portupgrade over apt-get any day. > > So definitely get a prototype of > > something working first. It's an easier sell that way. > > You _won't_ make it right basing on "prototypes". And you won't make headway saying "I haven't coded anything yet, but I need you to make these changes to your port". By "prototype", and mean a workable system with a handful of modified ports to demonstrate with. > > Stuff to be hashed out. Personally I think C/C++ is the best to > > code this in. > > Well, personally, I don't. We still need to define exactly what we want to do. If it's just modifying menus, then of course use Perl/Python/Ruby/Tcl/Etc. Heck, use bourne! But actually writing a new installer might entail C. A GUI that needs to be responsive might need to be in C++, depending on the toolkit. Fitting this all onto floppy number two for a network install might very well preclude most scripting languages in favor of a small tight C utility. p.s. Someone needs to set up a new list for this. David