From owner-freebsd-hackers@FreeBSD.ORG Sun May 20 23:15:58 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25DEE16A41F for ; Sun, 20 May 2007 23:15:58 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.freebsd.org (Postfix) with ESMTP id 0144E13C44C for ; Sun, 20 May 2007 23:15:57 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l4KNFvh2008585 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 20 May 2007 16:15:57 -0700 X-Auth-Received: from [192.168.10.45] (c-67-166-149-71.hsd1.ca.comcast.net [67.166.149.71]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l4KNFubo015500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 20 May 2007 16:15:57 -0700 Message-ID: <4650D6AC.4050405@u.washington.edu> Date: Sun, 20 May 2007 16:15:56 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20070513040651.GB1017@dwpc.dwlabs.ca> <4647F627.7020408@u.washington.edu> <20070514202922.GF1017@dwpc.dwlabs.ca> <4649426F.8050601@u.washington.edu> <1179214317.1791.38.camel@zoot.mintel.co.uk> <464969B3.3050306@u.washington.edu> <20070515213026.GI1017@dwpc.dwlabs.ca> <464D2195.3020309@u.washington.edu> <464F4FD9.9020308@u.washington.edu> In-Reply-To: <464F4FD9.9020308@u.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.5.20.155635 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Subject: Re: SoC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 23:15:58 -0000 Garrett Cooper wrote: > Garrett Cooper wrote: >> Duane Whitty wrote: >>> On Tuesday, 15 May 2007 at 1:05:07 -0700, Garrett Cooper wrote: >>>> Tom Evans wrote: >>>>> On Mon, 2007-05-14 at 22:17 -0700, Garrett Cooper wrote: >>>>>> Ruby's nice, but it's built on Perl so I have suspicions on its >>>>>> overall usability / speed given my experience with Perl over the >>>>>> past 4 months daily for work :(.. Ruby's just the new big thing >>>>>> for programming languages, so everyone's into it. Kind of like how >>>>>> Java was compared to C/C++ a few years back. But once everything >>>>>> dies down people will realize that they'll still have to program >>>>>> in C/C++/Perl for real-world applications. >>>>>> >>>>>> Python seems better than Ruby from what I can see, but I really >>>>>> don't like the mandatory indentation thing. Ew.. >>>>>> >>>>> Rubies are better Perls. That's the only connection between the >>>>> two. One >>>>> day, a Japanese programmer got fed up with Perl, and wrote a better >>>>> language (for varying meanings of better). >>>>> >>>>> Its not based or built on Perl in any respect. >>>>> >>>>> Python and Ruby both have the same targets; to speed development time >>>>> and increase programmer productivity. >>>> But one must make a Perl before one can make a Ruby. Maybe that was >>>> what I was trying to aim for. >>>> >>>> Ruby's nice, but it seems like it's going to be a bit passe in a few >>>> years like Java was for compilable / interpretable languages. >>>> >>>> -Garrett >> > >>> None of this matters >>> >>> >>> My only point is that if you need something quick to explore the >>> format of >>> pkgdb.db or INDEX.db you are pretty well assured of finding a tool you >>> can work with; Perl, Python, or Ruby. If these aren't sufficient use C. >>> >>> The pkg_* tools are written in C so in C they will be modified; but no >>> harm in doing initial exploration and prototyping with something else. >>> >>> Let's stay focused! >>> >>> Duane >> >> Ok, finally dumped the full database. Will analyze closely later on >> tonight. >> >> Cheers, >> -Garrett >> >> PS If you installed ruby-bdb, simply running "make config" in the >> ports-mgmt/portupgrade directory and selecting ruby-bdb1 won't do. You >> have to go into databases/ruby-bdb, do make deinstall, then go to >> databases/ruby-bdb1 and do make install, or something similar. > > If you haven't seen my entry yet, and you're interested, I've posted > my analysis of the INDEX-*.db file at: > . > I'd like to really discuss the additional metadata that gets tacked > onto each database file, in particular, is it necessary, and is there a > better way to do that? > Also, the whole Ruby ports tools writing to the ports db > consistently instead of at exit is another item which probably should be > discussed too (someone brought this up earlier). > Thanks, > -Garrett Posted more results here: . Needless to say, I'm not happy with Portupgrade. -Garret