From owner-freebsd-ports Sun Aug 20 00:15:06 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA14064 for ports-outgoing; Sun, 20 Aug 1995 00:15:06 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA14056 for ; Sun, 20 Aug 1995 00:15:02 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id AAA01154; Sun, 20 Aug 1995 00:14:55 -0700 Date: Sun, 20 Aug 1995 00:14:55 -0700 Message-Id: <199508200714.AAA01154@silvia.HIP.Berkeley.EDU> To: chuckr@Glue.umd.edu CC: ports@freebsd.org In-reply-to: (message from Chuck Robey on Wed, 16 Aug 1995 11:22:09 -0400 (EDT)) Subject: Re: do not try the tcl-7.4 port! From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * I have built the new libs, and tried the new version of tkman (not yet * ported) and rman and it works great, but I was too quick, I didn't try * the older apps. If this works, it sounds good. If you've tested it, * great, if you haven't, I would do it if you want. Well, I changed the names of the newer libs so that they won't coincide with the old ones in any way, but thanks anyway. I now have tkman and zircon both working on the same machine. Satoshi From owner-freebsd-ports Sun Aug 20 06:08:03 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id GAA28991 for ports-outgoing; Sun, 20 Aug 1995 06:08:03 -0700 Received: (from peter@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id GAA28969 ; Sun, 20 Aug 1995 06:07:48 -0700 Date: Sun, 20 Aug 1995 06:07:48 -0700 From: Peter Wemm Message-Id: <199508201307.GAA28969@freefall.FreeBSD.org> To: asami, ports, committers, rgrimes Subject: direct repository operation: ports/net/rdist -> ports/net/rdist6 Sender: ports-owner@FreeBSD.org Precedence: bulk Due to the conflict with the existing cvs module "rdist", and based on Satoshi's comments, and the "ncftp2" precedent, I have done: peter@freefall[5:56am]~ncvs/ports/net-101> l rdist total 6 1 drwxrwxr-x 5 peter ncvs 512 Aug 20 03:52 ./ 1 drwxrwxr-x 46 jkh ncvs 1024 Aug 20 03:51 ../ 1 -r--r--r-- 1 peter ncvs 731 Aug 19 06:51 Makefile,v 1 drwxrwxr-x 2 peter ncvs 512 Aug 20 03:52 files/ 1 drwxrwxr-x 2 peter ncvs 512 Aug 20 03:52 patches/ 1 drwxrwxr-x 2 peter ncvs 512 Aug 20 03:52 pkg/ peter@freefall[5:56am]~ncvs/ports/net-102> mkdir rdist6 peter@freefall[5:57am]~ncvs/ports/net-103> cp -p -r rdist/* rdist6 peter@freefall[5:58am]~ncvs/ports/net-104> l rdist6 total 6 1 drwxrwxr-x 5 peter ncvs 512 Aug 20 05:58 ./ 1 drwxrwxr-x 47 jkh ncvs 1024 Aug 20 05:58 ../ 1 -r--r--r-- 1 peter ncvs 731 Aug 19 06:51 Makefile,v 1 drwxrwxr-x 2 peter ncvs 512 Aug 20 05:58 files/ 1 drwxrwxr-x 2 peter ncvs 512 Aug 20 05:58 patches/ 1 drwxrwxr-x 2 peter ncvs 512 Aug 20 05:58 pkg/ peter@freefall[5:58am]~ncvs/ports/net-105> -Peter From owner-freebsd-ports Sun Aug 20 06:17:17 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id GAA29593 for ports-outgoing; Sun, 20 Aug 1995 06:17:17 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id GAA29586 for ; Sun, 20 Aug 1995 06:17:14 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id GAA03690 for ; Sun, 20 Aug 1995 06:17:06 -0700 To: ports@freebsd.org Subject: `make info'? Date: Sun, 20 Aug 1995 06:17:06 -0700 Message-ID: <3688.808924626@time.cdrom.com> From: "Jordan K. Hubbard" Sender: ports-owner@freebsd.org Precedence: bulk I think it's finally come to pass that we have too many ports.. :-) No, I'm not saying we need less - this is great! However, we now have too many to really make it easy to know what's available at a glance. For example, let's pretend for a moment that I'm a first-time user of the ports collection and I just want to get a feel for what it can offer me, so I cd to /usr/ports and do an ls: CVS benchmarks emulators net shells GUIDELINES cad games news sysutils INDEX comms graphics packages utils LEGAL databases japanese plan9 x11 Makefile devel lang print archivers distfiles mail russian audio editors math security Hmmm. Looks reasonably self-documenting so far - I can get a pretty good idea of what's available just by looking at all these nifty categories. Ah! I'm interested in emulators! Go to emulators and do an ls: CVS cpmemu hfs pcemu vmsbackup Makefile cpmtools mtools tkhfs wine Huh. the cpm* stuff is pretty obvious, as is vmsbackup I suppose, but tkhfs? mtools? wine? What are those? Where's the README? Sure, all of us know what those things are since we're familiar with the ports collection, but the first-timer? No, it's actually somewhat confusing, in fact! I think it's time that we considered this, and I have two quick suggestions just off the top of my head (there may be better ones of course): 1. Build an auto-generated README file at each level of the tree that's *human readable* as well as the INDEX at the top (which, someday RSN, I'll write a utility for actually using :-). 2. Add another target called `info' or something suitably mnemonic to the ports structure so that the user can type `make info' at any level of the tree to get a human readable dump of what's there. Document this option, along with other useful ones like `all' and `install' (we should never assume that the user just knows what to do), in a top level README and hope that the user is at least reasonable enough to read that first. Whatcha think, Satoshi? Jordan From owner-freebsd-ports Sun Aug 20 15:03:58 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id PAA22027 for ports-outgoing; Sun, 20 Aug 1995 15:03:58 -0700 Received: from eikon.e-technik.tu-muenchen.de (eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id PAA22019 ; Sun, 20 Aug 1995 15:03:53 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id AAA00145; Mon, 21 Aug 1995 00:02:40 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id TAA07319; Sat, 19 Aug 1995 19:04:50 +0200 Message-Id: <199508191704.TAA07319@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: ports@FreeBSD.org Cc: postmaster@FreeBSD.org Subject: Announcement of new list freebsd-hylafax@JHS_HOST_FOR_NOW In-reply-to: Your message of "Tue, 15 Aug 1995 23:01:16 CDT." <199508160401.XAA06302@starfire.mn.org> Date: Sat, 19 Aug 1995 19:04:47 +0200 From: "Julian Stacey " Sender: ports-owner@FreeBSD.org Precedence: bulk As maintainer of the freebsd comms/hylafax port, I have created a new list: freebsd-hylafax@vector.eikon.e-technik.tu-muenchen.de & this alias: freebsd-hylafax-request@vector.eikon.e-technik.tu-muenchen.de I would like to ask postmaster@freebsd.org to create a successor list: hylafax@freebsd.org (or perhaps freebsd-hylafax@freebsd.org) As vector.eikon.e-technik.tu-muenchen.de: - uses my 9K6 daily slip link, - is a mouthful of a hostname - isn't as appropriate as freefall anyway :-) - doesn't run majordomo yet, (I vi /etc/aliases + newaliases). If this proposal is acceptable to postmaster@freebsd.org, I will establish aliases for a while to freebsd.org from vector. The new list's remit: ------- - This list is for those interested in discussing the FreeBSD specific aspects of Hylafax. This is a self help group, not a place to give up & offload your problems ;-) Get the Hylafax source on FreeBSD from ports/comms/hylafax. - Hylafax generic aspects not unique to FreeBSD should be posted to flexfax@sgi.com, not here, ( echo "info flexfax" | mail majordomo@sgi.com) - Generic FreeBSD concerns that merely concern Hylafax as one of many FreeBSD ports, belong in lists such as ports@ or current@ or hackers@freebsd.org ( echo "info ports" | mail majordomo@freebsd.org) - The list will not be subscribed to either ports@freebsd.org or flexfax@sgi.com, senders should manually CC either (but not both) if they feel it truly appropriate. - The list is unmoderated ------- I have created an initial membership list of: jhs@freebsd.org,john@starfire.mn.org I can't find my list of freebsd hylafax people, So would they people (Lars Fredriksen, Andrei Chernov ? etc ) please mail freebsd-hylafax-request@vector.eikon.e-technik.tu-muenchen.de, I will later post a similar announcement to flexfax@sgi.com. I will add a suggestion to subscribe, to the ports/comms/hylafax/Makefile post-install: I realise we dont want a mail list for each freebsd port, but Hylafax is particularly big, with lots of tricky interfaces etc, hence need for the list, (A posting from john@starfire to ports@ was what sparked me to this idea). Julian From owner-freebsd-ports Sun Aug 20 15:04:23 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id PAA22118 for ports-outgoing; Sun, 20 Aug 1995 15:04:23 -0700 Received: from eikon.e-technik.tu-muenchen.de (eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id PAA22087 for ; Sun, 20 Aug 1995 15:04:15 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id AAA00176; Mon, 21 Aug 1995 00:03:57 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id MAA06715; Sat, 19 Aug 1995 12:13:28 +0200 Message-Id: <199508191013.MAA06715@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: asami@cs.berkeley.edu (Satoshi Asami) cc: gary@palmer.demon.co.uk, ports@FreeBSD.org Subject: Re: bsd.ports.mk checksum In-reply-to: Your message of "Sat, 19 Aug 1995 01:15:09 PDT." <199508190815.BAA05947@silvia.HIP.Berkeley.EDU> Date: Sat, 19 Aug 1995 12:13:27 +0200 From: "Julian Stacey " Sender: ports-owner@FreeBSD.org Precedence: bulk > Hey calm down. Your argument doesn't make much sense. You mean you > have all the sources extracted, but don't have the distfiles lying > around? EXACTLY ! I wrote you that already. Never heard of a CD-ROM ? It's used for distributing bulk computer data, but vendors don't distribute one drive per media disk ;-) When one has extracted & compiled 800M of ports, & starts to maintain ports off the net, & regularly compiles ports, if one takes the 200M of distfiles on the cd-rom off line, to look at other cd-roms, md5 fails on `make all'. > Then all I can say is that you are a distinct minority. No, You are the minority ! Just 3 people have expressed an opinion on this, (listed chronologically): - Julian S wants it removed - Gary P wrote : I'm not sure how this ever became the case, it certainly was never my intention to do this with the checksum mechanism, as I know from experience that doing a MD5 checksum on (say) emacs, when the distfile is on a CDROM, is painful. - Satoshi wants it to stay. That's 2:1 for removal so far. Though I have 3 Gig, I still don't want to waste 200M/250M keeping distfiles I've already compiled on line, others may not want to either. It's unfortunate that you force us to choose between wasting 200M, or abandoning automatic use of md5 on new ports. > This check is > added to save users from strange errors, It merely detect if the distfile has been mangled, gone missing or been changed, but once the user has a compiled source tree, this is not of vital interest, & the user can do a period check for this with a make checksum, if they're truly paranoid (Hey even _I'm_ not that paranoid on checks ;-). > and I am not going to remove it. I hope you don't stay this inflexible, (it discourages one from regularly recompiling the tree & reporting errors, when you make it neccessary to waste an extra 200/250M ). Perhaps pride of authorship & spare disc capacity blind you to the nuisance it imposes on others ? Was this extension of md5 usage discussed before it was CVS commited ? I hope it wasn't just slipped through by a minority of one ;-) ( perhaps after no one happened to notice the change during a test phase on a test system which luxuriates in all distfiles on line, & is thus unrepresentative ? ) > If the setenv works for you, then let's all be happy. :) No ! How can we be happy with a horrible cludge that exists merely to avoid a problem you impose ? Try asking people if they appreciate you forcing them to waste 200M/250M permanently keeping all distfiles on line ! As you raised the subject of minority, let's invite more opinions, meantime may I remind you that currently, To Please The Majority (2:1) you should: remove the md5 invocation from make all, & just leave it on make extract Thanks Julian S From owner-freebsd-ports Sun Aug 20 15:46:43 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id PAA25757 for ports-outgoing; Sun, 20 Aug 1995 15:46:43 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id PAA25751 for ; Sun, 20 Aug 1995 15:46:41 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id PAA03607; Sun, 20 Aug 1995 15:44:17 -0700 Date: Sun, 20 Aug 1995 15:44:17 -0700 Message-Id: <199508202244.PAA03607@silvia.HIP.Berkeley.EDU> To: jhs@vector.eikon.e-technik.tu-muenchen.de CC: gary@palmer.demon.co.uk, ports@FreeBSD.org In-reply-to: <199508191013.MAA06715@vector.eikon.e-technik.tu-muenchen.de> (jhs@vector.eikon.e-technik.tu-muenchen.de) Subject: Re: bsd.ports.mk checksum From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@FreeBSD.org Precedence: bulk * When one has extracted & compiled 800M of ports, & starts to maintain ports * off the net, & regularly compiles ports, if one takes the 200M of distfiles * on the cd-rom off line, to look at other cd-roms, md5 fails on `make all'. Well, I can add a variable to make it not abort at failed checksum errors. Is that ok for you? If you take the CDROM offline, you'll just get a warning message. By the way, if you want to do a "build all ports" check, the correct way to do this is to do a "make clean" and then "make package" (or "make install"). bsd.port.mk has been designed to work best that way. * I hope it wasn't just slipped through by a minority of one ;-) Hey, cut these kind of garbage, ok? Satoshi From owner-freebsd-ports Sun Aug 20 19:56:15 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id TAA06939 for ports-outgoing; Sun, 20 Aug 1995 19:56:15 -0700 Received: from lin.wsl.sinica.edu.tw (lin.wsl.sinica.edu.tw [140.109.7.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id TAA06878 for ; Sun, 20 Aug 1995 19:55:49 -0700 Message-Id: <199508210255.TAA06878@freefall.FreeBSD.org> Received: by lin.wsl.sinica.edu.tw (1.37.109.4/16.2) id AA23903; Mon, 21 Aug 95 10:33:09 +0800 From: Yen-Wei Liu Subject: Re: A better CHDIR for wu-ftpd-2.4 To: jdli@csie.nctu.edu.tw (Chien-Ta Lee) (Chien-Ta Lee) Date: Mon, 21 Aug 95 10:33:09 EAT Cc: freebsd-ports@freebsd.org In-Reply-To: <199508200613.OAA24271@phoenix.csie.nctu.edu.tw>; from "Chien-Ta Lee" at Aug 20, 95 2:12 pm Mailer: Elm [revision: 70.85] Sender: ports-owner@freebsd.org Precedence: bulk > > > Hi : > > Here is a patch to make wu-ftpd-2.4 can automatically search > directories when user CHDIR, it is ugly, but it works. > It should work on all OSs which wu-ftpd-2.4 supports. > I believe it still has the bug of failing to chdir to directory with leading "..", such as "cd ../foo", doesn't it ? -- Yen-Wei Liu Internet e-mail address:ywliu@beta.wsl.sinica.edu.tw ywliu@gate.sinica.edu.tw FAX: +886-2-783-6444 From owner-freebsd-ports Sun Aug 20 20:53:56 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id UAA11277 for ports-outgoing; Sun, 20 Aug 1995 20:53:56 -0700 Received: from ccsun8.csie.nctu.edu.tw (ccsun8.csie.nctu.edu.tw [140.113.209.13]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id UAA11267 for ; Sun, 20 Aug 1995 20:53:46 -0700 Received: (jdli@localhost) by ccsun8.csie.nctu.edu.tw (8.6.11/8.6.4) id LAA10472; Mon, 21 Aug 1995 11:52:45 +0800 From: jdli@csie.nctu.edu.tw (Chien-Ta Lee) Message-Id: <199508210352.LAA10472@ccsun8.csie.nctu.edu.tw> Subject: Re: A better CHDIR for wu-ftpd-2.4 To: ywliu@lin.wsl.sinica.edu.tw (Yen-Wei Liu) Date: Mon, 21 Aug 1995 11:52:45 +0800 (CST) Cc: freebsd-ports@FreeBSD.ORG In-Reply-To: <199508210245.KAA14198@phoenix.csie.nctu.edu.tw> from "Yen-Wei Liu" at Aug 21, 95 10:33:09 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 397 Sender: ports-owner@FreeBSD.ORG Precedence: bulk > > I believe it still has the bug of failing to chdir to directory > with leading "..", such as "cd ../foo", doesn't it ? > I never had this problem, maybe you can try to connect ftp.csie.nctu.edu.tw which use this patch, too. -- 不知何時, FreeBSD 悄悄的溜進了我可愛的小電腦.. 李 建 達 (Adonis) 交大資工 穩穩地生根了下來, 讓我心愛的PC魚躍翻身變成龍.. Mail: jdli@csie.nctu.edu.tw From owner-freebsd-ports Sun Aug 20 23:10:50 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id XAA28442 for ports-outgoing; Sun, 20 Aug 1995 23:10:50 -0700 Received: from Shug-Internet.Saar.DE (shug-internet.saar.de [192.109.53.4]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id XAA28421 for ; Sun, 20 Aug 1995 23:10:44 -0700 Received: from TMPuhf.Saar.DE (tmpuhf.saar.de [192.109.53.3]) by Shug-Internet.Saar.DE (8.6.8.1/8.5) with SMTP id IAA04189; Mon, 21 Aug 1995 08:10:11 +0200 Received: from ramsey by TMPuhf.Saar.DE with uucp (Smail3.1.28.1 #1) id m0skQ3m-000213C; Mon, 21 Aug 95 08:10 WET DST Received: by ramsey.saar.de (Smail3.1.29.1 #1) id m0skPsm-000OXJC; Mon, 21 Aug 95 07:58 MET DST Message-Id: Date: Mon, 21 Aug 95 07:58 MET DST From: torstenb@ramsey.saar.de (Torsten Blum) To: jdli@csie.nctu.EDU.TW Cc: ports@FreeBSD.ORG Subject: Re: A better CHDIR for wu-ftpd-2.4 References: <199508200613.OAA24271@phoenix.csie.nctu.edu.tw> Sender: ports-owner@FreeBSD.ORG Precedence: bulk > Here is a patch to make wu-ftpd-2.4 can automatically search > directories when user CHDIR, it is ugly, but it works. > It should work on all OSs which wu-ftpd-2.4 supports. please send your patch to wu-ftpd@wugate.wustl.edu (the wu-ftpd mailing list). From owner-freebsd-ports Sun Aug 20 23:26:06 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id XAA29287 for ports-outgoing; Sun, 20 Aug 1995 23:26:06 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id XAA29281 for ; Sun, 20 Aug 1995 23:26:04 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id XAA23886; Sun, 20 Aug 1995 23:25:57 -0700 Date: Sun, 20 Aug 1995 23:25:57 -0700 Message-Id: <199508210625.XAA23886@silvia.HIP.Berkeley.EDU> To: agc@uts.amdahl.com CC: thomas@ghpc8.ihf.rwth-aachen.de, ports@freebsd.org In-reply-to: (agc@uts.amdahl.com) Subject: Re: Postgres95 for FreeBSD From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * The release of Postgres95 will be in September (1995, for all you * cynics). Whilst it's true to say that the database format changed * between one of the beta cycles, there are also tools provided to * migrate your databases. As far as I can see, Postgres95 is more * stable than v4r2 (bugs have been fixed), and provides more * functionality as well as being quicker, so people might want to use * it. Sounds great...someone please make a port when it comes out...thanks... Satoshi From owner-freebsd-ports Mon Aug 21 06:09:55 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id GAA18673 for ports-outgoing; Mon, 21 Aug 1995 06:09:55 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id GAA18664 ; Mon, 21 Aug 1995 06:09:39 -0700 Received: by sequent.kiae.su id AA20667 (5.65.kiae-2 ); Mon, 21 Aug 1995 17:07:26 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 21 Aug 95 17:07:24 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id QAA00454; Mon, 21 Aug 1995 16:58:37 +0400 To: jkh@time.cdrom.com, Peter da Silva Cc: hackers@freebsd.org, ports@freebsd.org References: <199508211136.GAA09011@bonkers.taronga.com> In-Reply-To: <199508211136.GAA09011@bonkers.taronga.com>; from Peter da Silva at Mon, 21 Aug 1995 06:36:23 -0500 Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 21 Aug 1995 16:58:37 +0400 (MSD) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: Netscape and mime.types? Lines: 25 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 916 Sender: ports-owner@freebsd.org Precedence: bulk In message <199508211136.GAA09011@bonkers.taronga.com> Peter da Silva writes: >Jordan... >>Netscape has the annoying property of not dealing with .au files >>by default, but its default "Helper Applications and Proxies" page >>simply refers to a file named: >> /usr/local/lib/netscape/mime.types >>A file with which it is not distributed. >They assume you have a working metamail configuration already, and expect >you to point the entry at the existing mime.types file. >Metamail is really kind of soggy and hard to light. We already have metamail port. Maybe netscape port should EXEC_DEPEND on metamail port? -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-ports Mon Aug 21 14:48:35 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id OAA13704 for ports-outgoing; Mon, 21 Aug 1995 14:48:35 -0700 Received: from snoopy.mv.com (snoopy.mv.com [199.125.64.182]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id OAA13685 for ; Mon, 21 Aug 1995 14:48:25 -0700 Received: (from pw@localhost) by snoopy.mv.com (8.6.11/8.6.9) id RAA03654; Mon, 21 Aug 1995 17:45:09 -0400 Date: Mon, 21 Aug 1995 17:45:09 -0400 From: "Paul F. Werkowski" Message-Id: <199508212145.RAA03654@snoopy.mv.com> To: ports@freebsd.org Subject: CMUCL on FreeBSD Sender: ports-owner@freebsd.org Precedence: bulk There was a brief conversation in -hackers back in April regarding the availability of the subject port for FreeBSD. The short answer was "not now, maybe not ever". The discussion ended with an appeal for help porting it to Linux. That was then. Now I am sitting on a totally unique set of bits that previously ran ONLY on your favorite RISC workstation but now are quite happily infesting FreeBSD. I have managed to revive some x86 work that been abandoned several years ago and have the worlds first ever version of CMUCL (in alpha form) for Intel sand and FreeBSD. Truly the BMW of free Lisp ready rock on your own volkschip. So, if you always wanted a LISPM but had to settle for PC, are a hot shot hacker looking to meet your match, love Lisp (C won't help you here), and like what you see in the attached man page, here is your chance to take up the montyChallenge and win your 15-Sec of fame in the Lisp community. Aim your favorite WWW sucker at http://sayre.sysc.pdx.edu:80101/monty/ and pick up CMUCL-FreeBSD-alpha1.tar.{gz readme}. The tar file is 3.6MB and is a package-like thing ready to drop into /usr/local/lib containing a small startup executable that mmaps to a 10MB lisp.core. If you do that and want to help get this thing into beta -- maybe a package/port for 2.1 -- let me know and I'll show you the way. Note, that address is an fsp server and bandwidth limited to 1Kbyte/sec. It will take more than an hour to grab the bits. Have some fun. Paul Werkowski pw@snoopy.mv.com ---------------------cmucl.1------------------------------------- 1 NAME CMU Common Lisp DESCRIPTION CMU Common Lisp is public domain "industrial strength" Common Lisp programming environment. Many of the X3j13 changes have been incorporated into CMU CL. Wherever pos- sible, this has been done so as to transparently allow use of either CLtL1 or proposed ANSI CL. Probably the new features most interesting to users are SETF functions, LOOP and the WITH-COMPILATION-UNIT macro. HARDWARE REQUIREMENTS CMU CL is currently available for a variety of Unix work- stations. See the README file for current platforms. At least 16 megabytes of memory and 25 megabytes of disk space are recommended. As usual, more is better. OVERVIEW When compared other Common Lisp implementations, CMU CL has two broad advantages: -- The new CMU CL compiler (Python) is more sophisticated than other Common Lisp compilers. It both produces better code and is easier to use. -- The programming environment based on the Hemlock editor is better integrated than gnu-emacs based environments. (Though you can still use GNU if you want.) CMU CL also has significant non-technical advantages: -- It has good local support for CMU users, and is well integrated with the CMU CS environment. -- It is public domain, and is freely available to non-CMU sites that aren't able to afford a site-license for a commercial Lisp. COMPILER FEATURES The `Advanced Compiler' chapter of the User's manual extensively discusses Python's optimization capabilities (See DOCUMENTATION below.) Here are a few high points: -- Good efficiency and type-checking at the same time. Compiling code safe gives a 2x speed reduction at worst. October 15, 1991 1 -- In safe code, type declarations are verified, allowing declarations to be debugged in safe code. When you go to compile unsafe, you know the declarations are right. -- Full source level debugging of compiled code, including display of the exact call that got an error. -- Good efficiency notes that tell you why an operation can't be open coded or where you are number-consing, and that provide unprecedented source context -- Block compilation, partial evaluation, lightweight functions and proper tail-recursion allow low-cost use of function call abstraction. TYPE SUPPORT Important note: Even debugged programs may contain type errors that remain undetected by other compilers. When compiled with type checking suppressed using the CMU Com- mon Lisp compiler, these type errors may cause said debugged programs to die strangely. If type checking is not suppressed, these programs will die with an explicit type error. The most visible way in which Python differs from previous Common Lisp compilers is that it has a greater knowledge about types and a different approach to type checking. In particular, Python implements type checking which is `eager' and `precise': -- Eager in the sense that type checking is done immedi- ately whenever there is a declaration, rather than being delayed until the the value is actually used. For example: (let ((x ...)) (declare (fixnum x)) ...) Here, the type of the initial value of X must be a FIXNUM or an error will be signalled. -- Precise in the sense that the exact type specified is checked. For example, if a variable is declared to be of type (integer 3 7), then the value must always be an integer between 3 and 7. Since Python does more type checking, programs that work fine when compiled with other compilers may get type errors when compiled with Python. It is important to ini- tially compile programs with the default (safe) policy, and then test this version. If a program with an erro- neous declaration is compiled with type checking October 15, 1991 2 suppressed (due to the SAFETY optimize quality being reduced), then the type error may cause obscure errors or infinite looping. See the section `Getting Existing Pro- grams to Run' (6.6) in the compiler chapter of the user manual. CMU CL adheres to the X3J13 function type cleanup, which means that quoted lambda-lists are not of type FUNCTION, and are no longer directly callable. Use COERCE with the FUNCTION result type. OPTIMIZATION Python does many optimizations that are absent or less general in other Common Lisp compilers: Proper tail recur- sion, lightweight function call, block compilation, inter- procedural type inference, global flow analysis, dynamic type inference, global register allocation, stack number allocation, control optimization, integer range analysis, enhanced inline expansion, multiple value optimization and source-to-source transforms. Optimization and type-checking are controlled by the OPTI- MIZE declaration. The default compilation policy is type- safe. NUMERIC SUPPORT Python is particular good at number crunching: -- Good inline coding of float and 32 bit integer opera- tions, with no number consing. This includes all the hardware primitives ROUND, TRUNCATE, COERCE, as well as important library routines such as SCALE-FLOAT and DECODE-FLOAT. Results that don't fit in registers go on a special number stack. -- Full support for IEEE single and double (denorms, +-0, etc.) -- In block compiled code, numbers are passed as function arguments and return values in registers (and without number consing.) -- Calls to library functions (SIN, ...) are optimized to a direct call to the C library routine (with no number consing.) On hardware with direct support for such functions, these operations can easily be open-coded. -- Substantially better bignum performance than commer- cial implementations (2x-4x). Bignums implemented in lisp using word integers, so you can roll your own. October 15, 1991 3 Python's compiler warnings and efficiency notes are espe- cially valuable in numeric code. 50+ pages in the user manual describe Python's capabilities in more detail. THE DEBUGGER In addition to a Motif-based windowing interface and a basic command-line interface, the debugger also has sev- eral powerful new features: -- The "source" and "vsource" commands print the *precise* original source form responsible for the error or pend- ing function call. It is no longer necessary to guess which call to CAR caused some "not a list" error. -- Variables in compiled code can be accessed by name, so the debugger always evaluates forms in the lexical environment of the current frame. This variable access is robust in the presence of compiler optimization --- although higher levels of optimization may make vari- able values unavailable at some locations in the vari- able's scope, the debugger always errs on the side of discretion, refusing to display possibly incorrect val- ues. -- Compiled code can be stepped, stopping at each control transfer. -- Integration with the Hemlock editor. In a slave, the "edit" command causes the editor edit the source for the current code location. The editor can also send non-line-mode input to the debugger using C-M-H bind- ings. Try apropos "debug" in Hemlock. See the debugger chapter in the user manual for more details. We are working on integrating the debugger with Hemlock and X windows. THE GRAPHICAL INTERFACE CMU Common Lisp has an interface to Motif which is func- tionally similar to CLM, but works better in CMU CL. See: doc/motif-toolkit.doc doc/motif-internals.doc This motif interface has been used to write the inspector and graphical debugger. There is also a Lisp control panel with a simple file management facility, apropos and inspector dialogs, and controls for setting global options. October 15, 1991 4 Call INTERFACE:LISP-CONTROL-PANEL to create the control panel. When INTERFACE:*INTERFACE-STYLE* is :GRAPHICS (the default) and the DISPLAY environment variable is defined, the graphical inspector and debugger will be invoked by INSPECT or when an error is signalled. Possible values are :GRAPHICS and :TTY. If the value is :GRAPHICS, but there is no X display, then we quietly use the TTY inter- face. THE INTERPRETER As far as Common Lisp semantics are concerned, there is no interpreter; this is effectively a compile-only implemen- tation. Forms typed to the read-eval-print loop or passed to EVAL are in effect compiled before being run. In implementation, there is an interpreter, but it operates on the internal representation produced by the compiler's font-end. It is not recommended that programs be debugged by running the whole program interpreted, since Python and the debug- ger eliminate the main reasons for debugging using the interpreter: -- Compiled code does much more error checking than inter- preted code. -- It is as easy to debug compiled code as interpreted code. Note that the debugger does not currently support single- stepping. Also, the interpreter's pre-processing freezes in the macro definitions in effect at the time an inter- preted function is defined. Until we implement automatic reprocessing when macros are redefined, it is necessary to re-evaluate the definition of an interpreted function to cause new macro definitions to be noticed. DOCUMENTATION The CMU CL documentation is printed as tech reports, and is available (at CMU) in the document room: CMU Common Lisp User's Manual Hemlock User's Manual Hemlock Command Implementor's Manual Non-CMU users may get documentation from the doc/ direc- tory in the binary distribution: October 15, 1991 5 cmu-user.info CMU CL User's Manual in Gnu Info format. The ``cmu-user.info-'' files are subfiles. You can either have your EMACS maintainer install this in the info root, or you can use the info ``g(...whatever.../doc/cmu-user.info)'' command. cmu-user.ps The CMU CL User's Manual (148 pages) in postscript format. LaTeX source and DVI ver- sions are also available. release-notes.txt Information on the changes between releases. hemlock-user.ps Postscript version of the Hemlock User's Manual (124 pages.) hemlock-cim.ps Postscript version of the Hemlock Command Imple- mentor's Manual (96 pages). SUPPORT Bug reports should be sent to cmucl-bugs@cs.cmu.edu. Please consult your local CMU CL maintainer or Common Lisp expert to verify that the problem really is a bug before sending to this list. The CMU Common Lisp project is no longer funded, so only minimal support is being done at CMU. There is a net com- munity of who communicate via comp.lang.lisp and the cmucl-bugs@cs.cmu.edu mailing list. DISTRIBUTION CMU Common Lisp is a public domain implementation of Com- mon Lisp. Both sources and executables are freely avail- able via anonymous FTP; this software is "as is", and has no warranty of any kind. CMU and the authors assume no responsibility for the consequences of any use of this software. See the README file in the distribution for FTP instructions. ABOUT THE CMU COMMON LISP PROJECT Organizationally, CMU Common Lisp was a small, mostly autonomous part within the Mach operating system project. The CMU CL project was more of a tool development effort than a research project. The project started out as Spice Lisp, which provided a modern Lisp implementation for use in the CMU community. CMU CL has been under continuous October 15, 1991 6 development since the early 1980's (concurrent with the Common Lisp standardization effort.) Most of the CMU Com- mon Lisp implementors are now working on the Gwydion envi- ronment for Dylan (see http://legend.gwydion.cs.cmu.edu:8001/gwydion/.) CMU CL was funded by DARPA under CMU's "Research on Paral- lel Computing" contract. Rather than doing pure research on programming languages and environments, the emphasis was on developing practical programming tools. Sometimes this required new technology, but much of the work was in creating a Common Lisp environment that incorporates state-of-the-art features from existing systems (both Lisp and non-Lisp.) Because sources are freely available, CMU Common Lisp has been ported to experimental hardware, and used as a basis for research in programming language and environment con- struction. SEE ALSO lisp(1), README The ``CMU Common Lisp User's Manual'', the ``Hemlock User's Manual'', and the ``Hemlock Command Implementor's Manual'' October 15, 1991 7 ---------------------------------------------------------------- From owner-freebsd-ports Mon Aug 21 16:15:29 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id QAA17582 for ports-outgoing; Mon, 21 Aug 1995 16:15:29 -0700 Received: from web.azstarnet.com (azstarnet.com [169.197.1.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id QAA17568 ; Mon, 21 Aug 1995 16:15:25 -0700 Received: from sprite23.azstarnet.com (sprite23.azstarnet.com [169.197.3.23]) by web.azstarnet.com (8.6.10/8.6.10) with SMTP id QAA29757; Mon, 21 Aug 1995 16:13:20 -0700 Date: Mon, 21 Aug 1995 16:13:20 -0700 Message-Id: <199508212313.QAA29757@web.azstarnet.com> X-Sender: maher@azstarnet.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo@braae.ru.ac.za, questions@FreeBSD.org, ports@FreeBSD.org, FreeBSD-hackers@freefall.FreeBSD.org, FreeBSD-FAQ@freefall.FreeBSD.org From: maher@azstarnet.com (maher katbah) Subject: internet host Sender: ports-owner@FreeBSD.org Precedence: bulk Hi: can any body tell me where can I get the addresses or the phone number for the internet service provider . and how much the cost for those differant connections and what is the best way to go with, if I want to be an ISP for 200 users thank you From owner-freebsd-ports Mon Aug 21 18:42:19 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id SAA24159 for ports-outgoing; Mon, 21 Aug 1995 18:42:19 -0700 Received: from eikon.e-technik.tu-muenchen.de (eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id SAA24147 for ; Mon, 21 Aug 1995 18:42:13 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id DAA29106; Tue, 22 Aug 1995 03:42:01 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id CAA12973; Tue, 22 Aug 1995 02:01:14 +0200 Message-Id: <199508220001.CAA12973@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: asami@cs.berkeley.edu (Satoshi Asami) cc: gary@palmer.demon.co.uk, ports@freebsd.org Subject: Re: bsd.ports.mk checksum In-reply-to: Your message of "Sun, 20 Aug 1995 15:44:17 PDT." <199508202244.PAA03607@silvia.HIP.Berkeley.EDU> Date: Tue, 22 Aug 1995 02:01:13 +0200 From: "Julian Stacey " Sender: ports-owner@freebsd.org Precedence: bulk > Well, I can add a variable to make it not abort at failed checksum > errors. Is that ok for you? If you take the CDROM offline, you'll > just get a warning message. That's sounds a usable compromise, but I'd still prefer md5 didnt forcibly access distfiles, for ports that had already extracted succesfully. Could you ask Gary P for his views please ? > * I hope it wasn't just slipped through by a minority of one ;-) > Hey, cut these kind of garbage, ok? Is this too close to the truth ? Earlier you made a false assertion that I was advancing a minority view (re. md5), & based your intransigence to change on that assertion. If I had not debunked that assertion with a bit of gentle sarcasm, nothing would have changed. Questions: Was the extension of md5 checking to the `all' target proposed & discussed first, or just commited ? Was the author, reviewer, & committer one person ? Should FreeBSD ports changes have a minimum of 2 people ? Is anyone exempt from the 2 person rule ? Julian S From owner-freebsd-ports Mon Aug 21 19:09:41 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id TAA25059 for ports-outgoing; Mon, 21 Aug 1995 19:09:41 -0700 Received: from eikon.e-technik.tu-muenchen.de (eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id TAA25053 for ; Mon, 21 Aug 1995 19:09:35 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id EAA29276 for ; Tue, 22 Aug 1995 04:09:22 +0200 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) id EAA20524 for ports@freebsd.org; Tue, 22 Aug 1995 04:09:26 +0200 Date: Tue, 22 Aug 1995 04:09:26 +0200 From: Julian Howard Stacey Message-Id: <199508220209.EAA20524@vector.eikon.e-technik.tu-muenchen.de> To: ports@freebsd.org Subject: freebsd-hylafax Sender: ports-owner@freebsd.org Precedence: bulk That freebsd-hylafax list I created .... well the one on @vector.eikon.e-technik.tu-muenchen.de wont work at least for now, as the MX record has gone missing, perhaps there's one on freebsd.org by now anyway (I have just d/loaded 600 K of mail, there may be something from postmaster@freebsd.org about that for all I know ... yet PS I haven't set a reply-to:jhs@freebsd.org on this mail (didnt need to till my MX went missing :-( ) Julian S jhs@freebsd.org From owner-freebsd-ports Mon Aug 21 22:23:44 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id WAA03459 for ports-outgoing; Mon, 21 Aug 1995 22:23:44 -0700 Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id WAA03453 ; Mon, 21 Aug 1995 22:23:42 -0700 Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id WAA29668; Mon, 21 Aug 1995 22:23:30 -0700 Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id GAA06796 ; Tue, 22 Aug 1995 06:19:36 +0100 X-Message: This is a dial-up site. Quick responses to e-mails should not be relied upon. Thanks! To: "Julian Stacey" cc: ports@freebsd.org Subject: Re: bsd.ports.mk checksum In-reply-to: Your message of "Tue, 22 Aug 1995 02:01:13 +0200." <199508220001.CAA12973@vector.eikon.e-technik.tu-muenchen.de> Date: Tue, 22 Aug 1995 06:19:35 +0100 Message-ID: <6794.809068775@palmer.demon.co.uk> From: Gary Palmer Sender: ports-owner@freebsd.org Precedence: bulk In message <199508220001.CAA12973@vector.eikon.e-technik.tu-muenchen.de>, "Juli an Stacey " writes: >That's sounds a usable compromise, but I'd still prefer md5 didnt forcibly >access distfiles, for ports that had already extracted succesfully. >Could you ask Gary P for his views please ? Why does Satoshi have to ask my opinion? I really don't see the relevance of that question. My opinions have been stated already in public, which youself, Satoshi and everyone on the ports list have seen. >Earlier you made a false assertion that I was advancing a minority view >(re. md5), & based your intransigence to change on that assertion. >If I had not debunked that assertion with a bit of gentle sarcasm, >nothing would have changed. I would have to say it is the minority view. The ports mechanism is NOT designed to have the sources left lying around, in EXTRACTED form. It CANNOT handle this... (think about it - if it goes to the next version, there will still be a .extract_done or whatever lying around, and the system won't dare change anything, so you'll still have the old sources extracted). The ports system is decidedly compile, install and clean-up in one go, or be burnt. Making it otherwise would require taking bsd.port.mk to such a level of complexity that it probably would fail more often than it would work. Yes, I agree that the checksum routine should not be run at every step, but I think that your reasons are mis-founded. And throughout this discussion, you have YET to suggest a fix to this situation! Where's the patch to fix this problem? Why haven't I seen it? The ports system is a voluntary effort (probably more so than the main code tree), and I think it is unreasonable to go flinging mud (like you did in the message I am replying to) AND still expect us to go digging and impliment the fixes you want, when you have shown little inclination to do so youself. >Questions: > Was the extension of md5 checking to the `all' target proposed > & discussed first, or just commited ? I have no idea - I don't have the cvs log for bsd.port.mk locally. You have an account on freefall, why ask such a pointless question when it'd be easier for you to go find out the answer yourself instead of making other people do the leg work? > Was the author, reviewer, & committer one person ? See my last answer. And if it was, it wouldn't surprise me. Most of my work to bsd.port.mk has been done locally, and then committed to the tree to get feedback. To date, no-one has had a problem with any of my changes (other than my initial choice of names for the checksum stuff). > Should FreeBSD ports changes have a minimum of 2 people ? If we did follow this standard, no work would get done. Very few people who are `knowledgable' enough about the ports system to review such changes (myself included) have the time to review every change to the ports repository. I'm more than happy for someone to go an commit stuff, as it'd be their problem to clear up. > Is anyone exempt from the 2 person rule ? As far as I am concerned, for the ports tree, everyone is (perhaps excepting bsd.port.mk, which is too easy to screw up unless you know what you are doing). Since their name will be in the Makefile, the commit logs, and probably the $Id$ line, they are easy to chase up, and they only hurt themselves as their work will be viewed with some suspicion thereafter. And I have to say, this is fast becoming something that I'd prefer NOT seeing on any of the FreeBSD mailing lists (i.e. a slanging match). Either calm down, or take the next round off the freebsd-ports list. If I reeive another e-mail on this subject which still has the signature of a flamethrower, and it isn't in private, I won't answer it. Sorry, but I will not be responsible for propogating this in public. Yours Gary From owner-freebsd-ports Mon Aug 21 23:46:31 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id XAA07617 for ports-outgoing; Mon, 21 Aug 1995 23:46:31 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id XAA07611 ; Mon, 21 Aug 1995 23:46:27 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id XAA06375; Mon, 21 Aug 1995 23:44:53 -0700 From: "Rodney W. Grimes" Message-Id: <199508220644.XAA06375@gndrsh.aac.dev.com> Subject: Re: bsd.ports.mk checksum To: gary@palmer.demon.co.uk (Gary Palmer) Date: Mon, 21 Aug 1995 23:44:52 -0700 (PDT) Cc: jhs@freebsd.org, ports@freebsd.org In-Reply-To: <6794.809068775@palmer.demon.co.uk> from "Gary Palmer" at Aug 22, 95 06:19:35 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2500 Sender: ports-owner@freebsd.org Precedence: bulk ... > > I would have to say it is the minority view. The ports mechanism is > NOT designed to have the sources left lying around, in EXTRACTED > form. It CANNOT handle this... (think about it - if it goes to the > next version, there will still be a .extract_done or whatever lying > around, and the system won't dare change anything, so you'll still > have the old sources extracted). If it can't handle this, then the Makefile and/or .mk file is missing a dependency that would quickly fix the problem: .extract_done: Makefile Makefiles are almost always modified for any new version of the port due to source distribution changing. > The ports system is decidedly compile, install and clean-up in one go, > or be burnt. Making it otherwise would require taking bsd.port.mk to > such a level of complexity that it probably would fail more often than > it would work. It is missing a few dependencios for all the .magic cookies. .magic cookies with missing dependecies are a pain. I really hate it when I say ``make install'' and it don't do squat, I do a lot of NFS mounting, this .install_done cookie thing has no idea if this system has had the install run on it :-(. > Yes, I agree that the checksum routine should not be run at every > step, but I think that your reasons are mis-founded. > > And throughout this discussion, you have YET to suggest a fix to this > situation! Where's the patch to fix this problem? Here is mine for the .extract_done not causing an extract if the Makefile has changed because this is a new version of the port: [This is on a RELENG_2_1_0 branch, may need hand applying to -current] Index: bsd.port.mk =================================================================== RCS file: /home/ncvs/src/share/mk/bsd.port.mk,v retrieving revision 1.165 diff -c -r1.165 bsd.port.mk *** 1.165 1995/06/06 10:56:34 --- bsd.port.mk 1995/08/22 06:42:55 *************** *** 625,631 **** .if !target(extract) extract: checksum ${EXTRACT_COOKIE} ! ${EXTRACT_COOKIE}: @${ECHO_MSG} "===> Extracting for ${PKGNAME}" .if target(pre-extract) @${MAKE} ${.MAKEFLAGS} pre-extract --- 625,631 ---- .if !target(extract) extract: checksum ${EXTRACT_COOKIE} ! ${EXTRACT_COOKIE}: Makefile @${ECHO_MSG} "===> Extracting for ${PKGNAME}" .if target(pre-extract) @${MAKE} ${.MAKEFLAGS} pre-extract -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-ports Tue Aug 22 04:54:47 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id EAA21808 for ports-outgoing; Tue, 22 Aug 1995 04:54:47 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id EAA21791 ; Tue, 22 Aug 1995 04:54:43 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id EAA20365; Tue, 22 Aug 1995 04:54:19 -0700 Date: Tue, 22 Aug 1995 04:54:19 -0700 Message-Id: <199508221154.EAA20365@silvia.HIP.Berkeley.EDU> To: ache@astral.msk.su CC: jkh@time.cdrom.com, peter@bonkers.taronga.com, hackers@freebsd.org, ports@freebsd.org In-reply-to: (ache@astral.msk.su) Subject: Re: Netscape and mime.types? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * >They assume you have a working metamail configuration already, and expect * >you to point the entry at the existing mime.types file. * * >Metamail is really kind of soggy and hard to light. * * We already have metamail port. Maybe netscape port should * EXEC_DEPEND on metamail port? Uhh, if it's only one file, I don't want to add a dependency. At any rate, the mailcap is now part of netscape, so I think it's ok.... Satoshi From owner-freebsd-ports Tue Aug 22 05:38:21 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id FAA23169 for ports-outgoing; Tue, 22 Aug 1995 05:38:21 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id FAA23160 for ; Tue, 22 Aug 1995 05:38:14 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id FAA03651; Tue, 22 Aug 1995 05:38:05 -0700 Date: Tue, 22 Aug 1995 05:38:05 -0700 Message-Id: <199508221238.FAA03651@silvia.HIP.Berkeley.EDU> To: rgrimes@gndrsh.aac.dev.com CC: gary@palmer.demon.co.uk, ports@freebsd.org In-reply-to: <199508220644.XAA06375@gndrsh.aac.dev.com> (rgrimes@gndrsh.aac.dev.com) Subject: Re: bsd.ports.mk checksum From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk Hey guys, thanks...glad we are heading to a constructive discussion again. * If it can't handle this, then the Makefile and/or .mk file is missing * a dependency that would quickly fix the problem: * .extract_done: Makefile * * Makefiles are almost always modified for any new version of the port * due to source distribution changing. Well that's true if the Makefile has changed due to local editing. But let's not forget that the way that these things are usually updated (cvs or sup -- I don't know how ctm handles timestamps), the extract cookie having a newer timestamp than the Makefile doesn't really guarantee anything, although it will probably catch many cases. What we need is a framework to uniquely identify the distfile and the extracted tree. Even checksumming is not perfect, if both the new md5 file and the new distfile arrived via sup, bsd.port.mk will happily use the old extracted source. Maybe what we can do is to record the distfile checksum in the ${WRKDIR} area, and compare that to the md5 after the first time. This will save time, and I think it will also catch all but the most weird cases (like a new patch added to change the name of a file and PLIST updated to reflect the fact, but the user, having already done a build before those updates, installing the stuff with the old name and PLIST bombing on her face when trying to do a pkg_delete). Heck, we can even store the checksum of ALL the relevant files (Makefile, patches, package files etc.), that would be impossible to break (I'm only semi-serious here, mind you). * It is missing a few dependencios for all the .magic cookies. . * magic cookies with missing dependecies are a pain. I really hate * it when I say ``make install'' and it don't do squat, I do a lot of * NFS mounting, this .install_done cookie thing has no idea if this * system has had the install run on it :-(. There is a "reinstall" target to do exactly this, Rod.... :) Also, the preferred way to move stuff from one system to another is to use packages...and you don't even need the extracted source for this, the "package-noinstall" is a separate package rule that doesn't depend on install, so you can run it on a bare ports dir. * Here is mine for the .extract_done not causing an extract if the * Makefile has changed because this is a new version of the port: I'll hold on to this to a while, let's see if we can handle this with the "recorded checksum" idea above, 'cause it won't be necessary to check the Makefile then. Satoshi From owner-freebsd-ports Tue Aug 22 07:08:46 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id HAA26799 for ports-outgoing; Tue, 22 Aug 1995 07:08:46 -0700 Received: from eikon.e-technik.tu-muenchen.de (eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id HAA26787 for ; Tue, 22 Aug 1995 07:08:38 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id QAA10727; Tue, 22 Aug 1995 16:08:18 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id PAA07465; Tue, 22 Aug 1995 15:34:07 +0200 Message-Id: <199508221334.PAA07465@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: asami@cs.berkeley.edu (Satoshi Asami) cc: gary@palmer.demon.co.uk, ports@freebsd.org Subject: Re: pbasic-2.0-950813.tar.gz + pbasic-2.0-950813.src.tar.gz uploaded In-reply-to: Your message of "Sat, 19 Aug 1995 04:48:43 PDT." <199508191148.EAA26529@silvia.HIP.Berkeley.EDU> Date: Tue, 22 Aug 1995 15:34:06 +0200 From: "Julian Stacey " Sender: ports-owner@freebsd.org Precedence: bulk > * Err. freebsd.com? Aren't we getting ahead of ourselves here? I didn't > * know we had a ftp.FreeBSD.COM address :-) > > Hehe....I guess he meant freefall's LOCAL_PORTS. No, its a standard port, its not a money grabbing commercial licence thing :-) > By the way, I haven't received an answer to my question, did you > really really really reeeeeeeeeeally have to make a new tarball? Never saw the question. You imply there was an original tarball, I drink regularly with the author, a friend of 10 years, I've always been the one pushing him to tar it to an archive site. So which tarball are you thinking of, if not mine ? it's strange he never told me he'd put a modern copy, are you sure ? If so, URL please . > Yeah...well, it's mostly ok. The excessive comments after MAINTAINER > should go though, that's not what we want our users to read. If that's the `dont bother me' bit ? .... I am agreeable to that If I am not to be MAINTAINER (which I don't really want to be in fact) If I am to be MAINTAINER, it should stay. Your choice, I don't care either way. Also, what is ${LOCAL_}? Can't we just use ${PREFIX}? (without looking at Makefile) Sure, whatever :-) Julian S From owner-freebsd-ports Tue Aug 22 10:07:03 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id KAA04651 for ports-outgoing; Tue, 22 Aug 1995 10:07:03 -0700 Received: from tserv.lodgenet.com (dial21.iw.net [204.157.148.70]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id KAA04592 for ; Tue, 22 Aug 1995 10:05:37 -0700 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id MAA27596 for ; Tue, 22 Aug 1995 12:05:39 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.6.11/8.6.9) with SMTP id MAA26683 for ; Tue, 22 Aug 1995 12:04:05 -0500 Message-Id: <199508221704.MAA26683@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6 4/21/95 To: ports@freebsd.org Subject: ical 1.9 Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="===_0_Tue_Aug_22_12:03:41_CDT_1995" Date: Tue, 22 Aug 1995 12:04:02 -0500 From: "Eric L. Hernes" Sender: ports-owner@freebsd.org Precedence: bulk This is a multipart MIME message. --===_0_Tue_Aug_22_12:03:41_CDT_1995 Content-Type: text/plain; charset=us-ascii Here's a port of one of the better calendar programs I've seen. eric. --===_0_Tue_Aug_22_12:03:41_CDT_1995 Content-Type: text/plain; charset=us-ascii Content-Description: ical-port.tgz Content-Transfer-Encoding: x-uuencode begin 644 ical-port.tgz M'XL(```````"`^U:;6_C-A+.U^A73+'YD*2U+%F6E1B7PWIC-]4U=@++[=T! M"QBT1,NL]>*CJ#C>HOWM'4JVMW%E;^^`>`];/D@BB3,DYX405C?5T_0,LP6U:K93LV@&DTFLX)V"='0)X)P@%.*&?^[`#? M9^_SNV)?W?,)IFPVKA6C!-I]D\`4/Y M_]7Q!@9T"8N4BPS\-(JH+UB:0+Q>$3!->5OZ2*X3[0W\2'DFZ9S^)V>0N,*3*MMV6W+A-ON",SK:QL[_7.6QA^9-RB< M\9;SA`K=3V/M#7*>N<$9WFA=UQL-.OW>S:F4J2;GONV,>GPE)11QWAG]&*HNCOG^O._C;1JZ'XVS6/F".SM=OAV33K8@Z:IK/$C_*`PM\F6:!+W^KQ_._:_OTO/9W5 M/W?\Q_V/<0*7!^Y_J]%2\?]H\;_T?QS8GR?^@V/N^M]Q3!7_CX%^UX;S32#5 MT11Z^.$";N":3FW'">RKJTEP3:[MYL0VG(ES%5@F,9J-B7:B\,7L_\4\?,T: MX+^(_T[+DOF_:9A-%?^/ZO]NS[L=?I;X;S:Q<1/_';N(_RVGI>+_,7";+E:< MA3,!Y_Z%3,HMF*S`(\E/9`5W,QJ3)1&:YLKT_P91W@++@`#>T"1`Z_TNY=8! MO#2FD$Y!S"BP6*:?)!$PQ;H@YQ3[<0JU6DTKLMI+<`6-L?0@"4RVU0/0@,D+ M20((:$2+)I*Q:*57]8H)YKHBQ:)D@=V!)?!$.$OS#)9DE6V[2+F7+(JPVLD$ M,F-R'V`Y(TL8]6.R+U5)62)BFHB7/>5<"XZD0JJ(X1`H8PRI[^>?W7K%A(1;VDST0<:=IVP67%>BJA:7WID_6B*=+10@\_ MQ5E+HTF"OUVLZ.,-)]P^//Y[Z-Y]-RH,*;F2*0MQK4'F<[80TI`[`]T-?H#' M?(*+%NZ93Q-4\SRC5/LX%')8/19\G^[N7W_&XZ#\;^! M"8.*_\?ROTS],23#)R*[2OF_Y/W_>.]ZH]>9XQ/[OV&W/N[_EEF>_S8(V]?"#%K%)>>SYA)SR7!(;*ALQ"R!9IN-#-3D( MQY,\/$BGG*?\((=\\1]D2/+X(#T37)[U'F)9)9\@^P?HG!P87*:W^ZE%^D.C M`PRIGQ\P\"Q-YP?(<[K:3\2\]]#0/(_H`<>@42>'R/FB.(S>RR!FF/\'!^A^ MY&+._KQ#)<4WBRJQ241XU3K`UYJ0*7P%";/U)Q2T@A)@FBT]5[DT`[)Z8G19 M10G'A1A9-2U.$U2[FE;4&]4D3I*05I.6@:QZ_DB:T:A*+7DW%O19[*,]5Q'2 MJD:LA_9859*66&^E51:2?:HW8\R"1.;[%:0D%73/9`NLNJIL(S_%5#976_G` M<`C"MAN&^3E*OW_^_]3X0_>[TO0'_^_,^4!4!Q_F.K\[_C^[^XU@@Y M\OF?9=@;_YNVU9`M5E.=_QT%EY>7L/GW#YTEOYYZ1,`_\@@:%I;A\GN]8J'-_?U&>BFV)9=KZUKWMW(]_[`T] M]V'P5HYS=C[L7T!MNL-9DNX'8Z\<:*?G'[D+A3=RU^2)Y?\J=RT[MNB5+F@U M4!6G=$&A6]%PM='MA2+]3JE(=7-1&ZQI:RW'W,7]2#U"^K!^3= MZ;FN*K2O<8#P`UM`[3J9[N'9VAS?I>U=<>[==X64JHQ74%!04%!04%!04%!0 F4%!04%!04%!04%!04%!04%!04%!04%!04%#X"^$WI#^*6P!0``!0 ` end --===_0_Tue_Aug_22_12:03:41_CDT_1995 Content-Type: text/plain; charset=us-ascii -- erich@lodgenet.com erich@rrnet.com --===_0_Tue_Aug_22_12:03:41_CDT_1995-- From owner-freebsd-ports Tue Aug 22 10:24:11 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id KAA05360 for ports-outgoing; Tue, 22 Aug 1995 10:24:11 -0700 Received: from eikon.e-technik.tu-muenchen.de (eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id KAA05351 for ; Tue, 22 Aug 1995 10:24:01 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id TAA14795; Tue, 22 Aug 1995 19:23:36 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id RAA10455; Tue, 22 Aug 1995 17:53:44 +0200 Message-Id: <199508221553.RAA10455@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: Gary Palmer cc: ports@freebsd.org Subject: Re: bsd.ports.mk checksum In-reply-to: Your message of "Tue, 22 Aug 1995 06:19:35 BST." <6794.809068775@palmer.demon.co.uk> Date: Tue, 22 Aug 1995 17:53:43 +0200 From: "Julian Stacey " Sender: ports-owner@freebsd.org Precedence: bulk > The ports system is decidedly compile, install and clean-up in one go, > or be burnt. Making it otherwise would require taking bsd.port.mk to > such a level of complexity that it probably would fail more often than > it would work. I run a current ports tree, invoking `make all' each day, to top up with new ports, in the same way one makes src/, works fine. I'm not bothered if someone upgrades to a new distfile, I ignore till a make clean. The ports tree & mk files actually support this quite well. > you have YET to suggest a fix to this situation! Huh ? Have you forgotten what I proposed: Back out the md5 invocation used by `make all' from ports.mk, Leave invocation on extract. > Yes, I agree that the checksum routine should not be run at every > step, Good, perhaps you can persuade Satoshi ? > but I think that your reasons are mis-founded. Suffice we want the same thing, why we want it doesn't matter :-) > Expect us to go digging and impliment the fixes Pointless me writing a patch till we agree what we need Eh ? Even then, better for you or Satoshi to do it, you'r the regular ports guys. `Too many cooks spoil the broth' I don't approve un-necessary working in other's backyards, I prefer to leave ports mechanism to others, & worry about my own area (Hylafax, Pbasic). > You have an account on freefall, why ask such a pointless question > when it'd be easier for you to go find out the answer yourself instead > of making other people do the leg work? You seem to have lost context or inference, & don't seem v. calm, so I'll pass. > > Is anyone exempt from the 2 person rule ? > As far as I am concerned, for the ports tree, everyone is (perhaps > excepting bsd.port.mk, Sigh - ports mk is what the proposal is all about ! > Either calm down But I am ! Even though Satoshi also asked me to calm down :-) (BTW: Ever heard the old joke about how to make an Irishman angry ? 1st Questioner: Why are all you Irish argumentative ? Respondent: We're not :-) 2nd Questioner: Why are all you Irish argumentative ? Respondent: We're Not. ... Respondent: We're NOT ! ... (With apologies to Ireland, which I like :-) Anyway, calmly :-) ... I aim to allow us to maintain an 800M ports/ online pre-compiled, but without the burden of an extra 250M distfiles permanently on line (IMO intermittent on line via a CD is enough), We're nearly there, we just need a tweak to the md5 invocation in ports.mk. (Having the sources permanently laid out in a tree makes a great way to explore & experimentally tweak code). > signature of a flamethrower Pardon ? I recall no personal abuse issued or received, The Issue: I propose we modify ports.mk so there is no md5 invocation by `make all' from ports.mk, but so there is invocation on `extract'. If you agree, please discuss it with Satoshi, who seemed less atracted to it, and come to a common agreed objective (a task description). If I agree with your task description, I will write the diff for you, if you want me to. So ... you only have to discuss & agree (& not even with me :-) & If I agree your mutual objective I'll do the work for you, (& if I don't, well, you wouldn't want me to write it, would you ?) Can't be fairer than that Eh ? Julian S From owner-freebsd-ports Tue Aug 22 12:11:30 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id MAA10918 for ports-outgoing; Tue, 22 Aug 1995 12:11:30 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id MAA10783 ; Tue, 22 Aug 1995 12:10:19 -0700 Received: by sequent.kiae.su id AA12098 (5.65.kiae-2 ); Tue, 22 Aug 1995 23:06:41 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 22 Aug 95 23:06:39 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id WAA00147; Tue, 22 Aug 1995 22:48:44 +0400 To: Satoshi Asami Cc: hackers@freebsd.org, jkh@time.cdrom.com, peter@bonkers.taronga.com, ports@freebsd.org References: <199508221154.EAA20365@silvia.HIP.Berkeley.EDU> In-Reply-To: <199508221154.EAA20365@silvia.HIP.Berkeley.EDU>; from Satoshi Asami at Tue, 22 Aug 1995 04:54:19 -0700 Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 22 Aug 1995 22:48:44 +0400 (MSD) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: Netscape and mime.types? Lines: 23 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 965 Sender: ports-owner@freebsd.org Precedence: bulk In message <199508221154.EAA20365@silvia.HIP.Berkeley.EDU> Satoshi Asami writes: > * >They assume you have a working metamail configuration already, and expect > * >you to point the entry at the existing mime.types file. > * > * >Metamail is really kind of soggy and hard to light. > * > * We already have metamail port. Maybe netscape port should > * EXEC_DEPEND on metamail port? >Uhh, if it's only one file, I don't want to add a dependency. At any >rate, the mailcap is now part of netscape, so I think it's ok.... BTW, I saw _two_ files in somebody mail: mime.types and mailcap. I saw commit addition of only _one_ file (mailcap?). Maybe I miss something? -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-ports Tue Aug 22 17:42:27 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id RAA27473 for ports-outgoing; Tue, 22 Aug 1995 17:42:27 -0700 Received: from web.azstarnet.com (azstarnet.com [169.197.1.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id RAA27466 ; Tue, 22 Aug 1995 17:42:25 -0700 Received: from dialup98.azstarnet.com (dialup97.azstarnet.com [169.197.2.97]) by web.azstarnet.com (8.6.10/8.6.10) with SMTP id RAA00157; Tue, 22 Aug 1995 17:40:22 -0700 Date: Tue, 22 Aug 1995 17:40:22 -0700 Message-Id: <199508230040.RAA00157@web.azstarnet.com> X-Sender: maher@azstarnet.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo@braae.ru.ac.za, questions@FreeBSD.org, ports@FreeBSD.org, FreeBSD-hackers@freefall.FreeBSD.org, FreeBSD-FAQ@freefall.FreeBSD.org From: maher@azstarnet.com (maher katbah) Subject: internet host Sender: ports-owner@FreeBSD.org Precedence: bulk Hi everybody I am trying to setup an internet server in tucson Arizona , and I am looking for internet host who can lease T1 line, I need some help from those who know the answer.Please let me know if there is a newsgroup for ISP. Thank you maher From owner-freebsd-ports Tue Aug 22 18:13:43 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id SAA29138 for ports-outgoing; Tue, 22 Aug 1995 18:13:43 -0700 Received: from forgery.CS.Berkeley.EDU (forgery.CS.Berkeley.EDU [128.32.33.75]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id SAA29130 for ; Tue, 22 Aug 1995 18:13:41 -0700 Received: (from asami@localhost) by forgery.CS.Berkeley.EDU (8.6.11/8.6.9) id SAA02642; Tue, 22 Aug 1995 18:14:37 -0700 Date: Tue, 22 Aug 1995 18:14:37 -0700 Message-Id: <199508230114.SAA02642@forgery.CS.Berkeley.EDU> To: ports@freebsd.org In-reply-to: <199508221334.PAA07465@vector.eikon.e-technik.tu-muenchen.de> (jhs@vector.eikon.e-technik.tu-muenchen.de) Subject: Re: pbasic-2.0-950813.tar.gz + pbasic-2.0-950813.src.tar.gz uploaded From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk Julian, I recommend you go read the porting guidelines, it's section 4.3 of the handbook (http://www.freebsd.org/How/handbook) or porting.sgml in FreeBSD-current/src/share/doc/handbook. * No, its a standard port, its not a money grabbing commercial licence thing :-) This has nothing to do with the licensing. Please read the guidelines.... * > By the way, I haven't received an answer to my question, did you * > really really really reeeeeeeeeeally have to make a new tarball? * * Never saw the question. I sent one to you. Should be in the ports archive. * You imply there was an original tarball, There was a message by Michael Smith (msmith@atrad.adelaide.edu.au) to this list about the availability of pbasic on some ftp site, alongside with bwbasic. Oh yeah, alongside with bwbasic...checking bwbasic's Makefile, I found it: ftp://ftp.eng.umd.edu/pub/basic/ * Your choice, I don't care either way. I'd prefer we delete the MAINTAINER along with the comments. * Also, what is ${LOCAL_}? Can't we just use ${PREFIX}? * (without looking at Makefile) Sure, whatever :-) Julian, please read the ports guidelines first, ok? Satoshi From owner-freebsd-ports Tue Aug 22 20:01:07 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id UAA03121 for ports-outgoing; Tue, 22 Aug 1995 20:01:07 -0700 Received: from misery.sdf.com (gw.sdf.com [204.191.196.33]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id UAA03100 for ; Tue, 22 Aug 1995 20:00:44 -0700 Received: by misery.sdf.com id <1080>; Tue, 22 Aug 1995 19:55:47 +0100 Date: Tue, 22 Aug 1995 19:55:30 -0700 (PDT) From: Tom Samplonius To: Jim Lowe cc: ports@freebsd.org Subject: Re: Samba In-Reply-To: <199508221736.MAA18144@miller.cs.uwm.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ports-owner@freebsd.org Precedence: bulk On Tue, 22 Aug 1995, Jim Lowe wrote: > > Has anyone ported Samba to FreeBSD yet? For more information the > URL is: > http://lake.canberra.edu.au/pub/samba/samba.html For longer than I can remeber: check .../ports/net/samba BTW, this does not belong on "freebsd-hackers", because that is what "freebsd-ports" is for. Tom From owner-freebsd-ports Tue Aug 22 22:51:38 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id WAA12496 for ports-outgoing; Tue, 22 Aug 1995 22:51:38 -0700 Received: from web.azstarnet.com (azstarnet.com [169.197.1.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id WAA12489 ; Tue, 22 Aug 1995 22:51:37 -0700 Received: from dialup98.azstarnet.com (dialup64.azstarnet.com [169.197.2.64]) by web.azstarnet.com (8.6.10/8.6.10) with SMTP id WAA01965; Tue, 22 Aug 1995 22:49:58 -0700 Date: Tue, 22 Aug 1995 22:49:58 -0700 Message-Id: <199508230549.WAA01965@web.azstarnet.com> X-Sender: maher@azstarnet.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo@braae.ru.ac.za, questions@FreeBSD.org, ports@FreeBSD.org, FreeBSD-hackers@freefall.FreeBSD.org, FreeBSD-FAQ@freefall.FreeBSD.org From: maher@azstarnet.com (maher katbah) Subject: Boca multiport card Sender: ports-owner@FreeBSD.org Precedence: bulk Hi Does anybody know if Boca 16 ports card would work with freebsd 2.0.5 ? and can you use two of them? instad of terminal server, please include a hint how to configuer the server and the modems with them Is there any software needs to be run on the top of the FreeBSD2.0.5 to run Web server and what is the name of it? thank you From owner-freebsd-ports Wed Aug 23 00:07:41 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA15112 for ports-outgoing; Wed, 23 Aug 1995 00:07:41 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA15103 ; Wed, 23 Aug 1995 00:07:38 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id AAA03521; Wed, 23 Aug 1995 00:04:39 -0700 To: ache@astral.msk.su cc: Satoshi Asami , hackers@freebsd.org, peter@bonkers.taronga.com, ports@freebsd.org Subject: Re: Netscape and mime.types? In-reply-to: Your message of "Tue, 22 Aug 1995 22:48:44 +0400." Date: Wed, 23 Aug 1995 00:04:39 -0700 Message-ID: <3519.809161479@time.cdrom.com> From: "Jordan K. Hubbard" Sender: ports-owner@freebsd.org Precedence: bulk > BTW, I saw _two_ files in somebody mail: mime.types and mailcap. > I saw commit addition of only _one_ file (mailcap?). > Maybe I miss something? I think that mime.types is actually the "built in" part that Netscape aludes to in their FAQ. The mailcap file was the key missing component for me, and once I added it netscape did the right thing and did it rather well. It even asks me if I want to play the MPEG audio files directly or save them first to disk (to a temp file which it deletes) first. This makes it work well with both high-bandwidth and low-bandwidth links and you don't have to manage the temp files yourself for things you just want to listen to once and throw away. [If you do want to save it outright, you can always hold the shift key down as usual]. Jordan From owner-freebsd-ports Wed Aug 23 02:20:17 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id CAA22768 for ports-outgoing; Wed, 23 Aug 1995 02:20:17 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id CAA22762 for ; Wed, 23 Aug 1995 02:20:14 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id CAA01551; Wed, 23 Aug 1995 02:19:13 -0700 Date: Wed, 23 Aug 1995 02:19:13 -0700 Message-Id: <199508230919.CAA01551@silvia.HIP.Berkeley.EDU> To: erich@lodgenet.com CC: ports@freebsd.org In-reply-to: <199508221704.MAA26683@jake.lodgenet.com> (erich@lodgenet.com) Subject: Re: ical 1.9 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * Here's a port of one of the better * calendar programs I've seen. Hmm, can't compile it here (thud, even reinstalled tcl-7.3 and tk-3.6). :< Satoshi ------- : c++ -O -I. -I. -I./calendar -I./types -I./time -I/usr/X11R6/include -I/usr/local/include -I/usr/local/include -c item_tcl.C c++ -O -I. -I. -I./calendar -I./types -I./time -I/usr/X11R6/include -I/usr/local/include -I/usr/local/include -c object.C c++ -O -I. -I. -I./calendar -I./types -I./time -I/usr/X11R6/include -I/usr/local/include -I/usr/local/include -c time_tcl.C cc -O -I. -I. -I/usr/X11R6/include -I/usr/local/include -I/usr/local/include -c tclmain.c cc -O -I. -I. -I/usr/X11R6/include -I/usr/local/include -I/usr/local/include -c tkmain.c In file included from tkmain.c:22: copies/tkMain.c:53: parse error before `mainWindow' copies/tkMain.c:53: warning: data definition has no type or storage class copies/tkMain.c:79: parse error before `argTable' copies/tkMain.c:80: warning: braces around scalar initializer for `argTable[0]' copies/tkMain.c:80: warning: initialization makes integer from pointer without a cast copies/tkMain.c:80: `TK_ARGV_STRING' undeclared here (not in a function) copies/tkMain.c:80: warning: excess elements in scalar initializer after `argTable[0]' copies/tkMain.c:80: warning: excess elements in scalar initializer after `argTable[0]' copies/tkMain.c:80: warning: excess elements in scalar initializer after `argTable[0]' : From owner-freebsd-ports Wed Aug 23 02:40:48 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id CAA24267 for ports-outgoing; Wed, 23 Aug 1995 02:40:48 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id CAA24261 for ; Wed, 23 Aug 1995 02:40:45 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id CAA02892; Wed, 23 Aug 1995 02:40:37 -0700 Date: Wed, 23 Aug 1995 02:40:37 -0700 Message-Id: <199508230940.CAA02892@silvia.HIP.Berkeley.EDU> To: erich@lodgenet.com CC: ports@freebsd.org In-reply-to: <199508230919.CAA01551@silvia.HIP.Berkeley.EDU> (asami@cs.berkeley.edu) Subject: Re: ical 1.9 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk I tried it again at home (2.1-stable), it compiles fine. I guess I need to go fix thud again (sigh). Satoshi From owner-freebsd-ports Wed Aug 23 03:14:30 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id DAA26364 for ports-outgoing; Wed, 23 Aug 1995 03:14:30 -0700 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id DAA26336 ; Wed, 23 Aug 1995 03:14:12 -0700 Received: by sovcom.kiae.su id AA02169 (5.65.kiae-1 ); Wed, 23 Aug 1995 13:06:53 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Wed, 23 Aug 95 13:06:53 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id OAA00904; Wed, 23 Aug 1995 14:01:35 +0400 To: "Jordan K. Hubbard" Cc: Satoshi Asami , hackers@freebsd.org, peter@bonkers.taronga.com, ports@freebsd.org References: <3519.809161479@time.cdrom.com> In-Reply-To: <3519.809161479@time.cdrom.com>; from "Jordan K. Hubbard" at Wed, 23 Aug 1995 00:04:39 -0700 Message-Id: Organization: Olahm Ha-Yetzirah Date: Wed, 23 Aug 1995 14:01:35 +0400 (MSD) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: Netscape and mime.types? Lines: 21 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1003 Sender: ports-owner@freebsd.org Precedence: bulk In message <3519.809161479@time.cdrom.com> Jordan K. Hubbard writes: >> BTW, I saw _two_ files in somebody mail: mime.types and mailcap. >> I saw commit addition of only _one_ file (mailcap?). >> Maybe I miss something? >I think that mime.types is actually the "built in" part that Netscape >aludes to in their FAQ. The mailcap file was the key missing mime.types is needed for format extensions: i.e. when I want to handle in my browser VRML (Virtual Reality Markup Language) [.vrm] or RealAudio [.ra], I need to add those types to make them known. I can't check right now, does U*IX Netscape have ability interactively add extensions and viewers? If not, we need to add mime.types too for this purpose. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-ports Wed Aug 23 03:17:53 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id DAA26658 for ports-outgoing; Wed, 23 Aug 1995 03:17:53 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id DAA26651 for ; Wed, 23 Aug 1995 03:17:45 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id SAA03696; Wed, 23 Aug 1995 18:17:29 +0800 Date: Wed, 23 Aug 1995 18:17:29 +0800 From: Brian Tao Message-Id: <199508231017.SAA03696@aries.ibms.sinica.edu.tw> To: freebsd-ports@freebsd.org Subject: Re: Announcing DNEWS 1.0c NNTP Server (NT, VMS, UNIX) Newsgroups: news.software.nntp,comp.os.vms In-Reply-To: <303950c2.0@news.palm.cri.nz> Organization: Institute of Biomedical Sciences, Academia Sinica Sender: ports-owner@freebsd.org Precedence: bulk Anyone interested in looking at the source for this new news server and see how well it builds under FreeBSD (and then offer a binary back to the maintainer)? In article <303950c2.0@news.palm.cri.nz> netwin@world.std.com writes: > >DNEWS is a dynamic news server system, it is not a news reader! > >DNEWS Feature list: > Dynamic sucking feed. > A sucking feed may use as little as 10% of the normal > disk space and network bandwidth. > By only getting news items that people usually read > very large savings are possible particularly for small > sites & workgroups. A hundred users can be supported > on 100 MB depending on their reading habbits! > I run a single user server on my NT as a background > service, it's using less than 5MB. > Flexible expire settings > By allowing expiration by 'number of items' low volume groups > become much more useful. Also by allowing settings > which change with disk space the system is much more > stable to large influxes of news. > Binarys available for common platforms > On many platforms you do not need to build the binary > yourself, e.g. VMS, (VAX & ALPHA), Solaris, Linux, Windows NT > Email confirmation of posts > DNEWS can be configured to send email confirmations as it > sends items up to a main news server. This gives users > a clear record of a posted item and it's successful > transfer into the 'net'. > Items stored in a database > Items are stored in a database which puts items together > in blocks of 100. This saves directory entries, inodes, > and the empty space usually wasted due to blocking factors. > Also file open and closes are minimized, this is essential > on systems where this is a 'costly' operation, e.g. VMS. > Compiling and porting relatively easy > DNEWS was designed to be portable from the ground up, it > does not rely on obscure UNIX features. > Installation easy, totally configurable without recompiling > DNEWS can be configured without recompiling and all > the configuration scripts have been simplified where > possible. > Documentated > A user manual is available. > Supported > EMAIL support is available for help with installation > and management. > Speed > On comparable systems DNEWS typically out performs other > news software, (even the likes of CNEWS and INN in some > instances), other VMS news servers don't even come close. > This is partly because DNEWS uses a more advanced database > to store the news items. The difference is also very > noteable on smaller systems (e.g. Linux) > XOVER implemented in software > No xover database is created, the normal DNEWS database > is fast enough to create this information 'on the fly' > Streaming support > Streaming NNTP extensions are built in. > Strictly limited machine impact > DNEWS runs in a single process, this speeds up connect > time as a process does not need to be created, and it > self-limits the impact on the system. >Limitations: > DNEWS does not store items in the same file structure as used by > INN and CNEWS, so old software which accesses these files directly > will not work. >----------------------------------------------------------------------------- >Upload binarys or source from: > ftp.std.com /ftp/vendors/netwin/dnews >For more details upload > ftp.std.com /ftp/vendors/netwin/dnews/install.txt > >Binaries are available for VMS, (VAX & ALPHA), Solaris, Linux, Windows NT >Source is available on request, see source.txt in the ftp site > > http://world.std.com/~netwin >----------------------------------------------------------------------------- > > netwin@world.std.com -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-ports Wed Aug 23 03:36:38 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id DAB27563 for ports-outgoing; Wed, 23 Aug 1995 03:36:38 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id DAA27555 for ; Wed, 23 Aug 1995 03:36:36 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id DAA04731; Wed, 23 Aug 1995 03:36:21 -0700 To: asami@cs.berkeley.edu (Satoshi Asami) cc: erich@lodgenet.com, ports@freebsd.org Subject: Re: ical 1.9 In-reply-to: Your message of "Wed, 23 Aug 1995 02:40:37 PDT." <199508230940.CAA02892@silvia.HIP.Berkeley.EDU> Date: Wed, 23 Aug 1995 03:36:21 -0700 Message-ID: <4728.809174181@time.cdrom.com> From: "Jordan K. Hubbard" Sender: ports-owner@freebsd.org Precedence: bulk > I tried it again at home (2.1-stable), it compiles fine. I guess I > need to go fix thud again (sigh). > > Satoshi Do you want me to spam thud down to the metal? Would it help? You're free to have whatever done to that machine you feel is most conducive to your work! Jordan From owner-freebsd-ports Wed Aug 23 04:01:09 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id EAA28242 for ports-outgoing; Wed, 23 Aug 1995 04:01:09 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id EAA28230 for ; Wed, 23 Aug 1995 04:01:00 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id TAA03754; Wed, 23 Aug 1995 19:00:50 +0800 Date: Wed, 23 Aug 1995 19:00:49 +0800 (CST) From: Brian Tao To: freebsd-ports@freebsd.org Subject: Re: Announcing DNEWS 1.0c NNTP Server (NT, VMS, UNIX) In-Reply-To: <199508231017.SAA03696@aries.ibms.sinica.edu.tw> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ports-owner@freebsd.org Precedence: bulk On Wed, 23 Aug 1995, Brian Tao wrote: > > Anyone interested in looking at the source for this new news > server and see how well it builds under FreeBSD (and then offer a > binary back to the maintainer)? > > In article <303950c2.0@news.palm.cri.nz> netwin@world.std.com writes: > > [...] > >Binaries are available for VMS, (VAX & ALPHA), Solaris, Linux, Windows NT > >Source is available on request, see source.txt in the ftp site > > > > http://world.std.com/~netwin I've included the source.txt file below. We can easily get in through clause #1 and #3... >>>>> Source Source is available, but for commercial reasons we require a statement of non-competition and non re-distribution before making it available. We appologize for the inconvenience this may cause. Source is made available to make the following possible. 1) Customers to port to various unix platforms 2) Checking for virus'es etc 3) Enhancements and bug fixing by technically inclined customers. Fill out this form and mail it to netwin@world.std.com to obtain source: ------------ cut here ---------------- Request for DNEWS source Please send instructions for FTPing the source, we need access to the source for INTERNAL use ONLY. We WILL NOT re distribute the source in any form. We are not in the business of selling NEWS SERVER software. Company: Your Name: Email Address: Physical MAIL Address: Phone number: Fax number: <<<<< -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-ports Wed Aug 23 04:38:51 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id EAA28908 for ports-outgoing; Wed, 23 Aug 1995 04:38:51 -0700 Received: from quebecweb.com (www.quebecweb.com [199.45.69.107]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id EAA28897 for ; Wed, 23 Aug 1995 04:38:32 -0700 Received: (from root@localhost) by quebecweb.com (8.6.9/8.6.9) id HAA22123 for ports@FreeBSD.org; Wed, 23 Aug 1995 07:26:10 -0400 Date: Wed, 23 Aug 1995 07:26:10 -0400 From: Mario Verville Message-Id: <199508231126.HAA22123@quebecweb.com> To: ports@FreeBSD.org Sender: ports-owner@FreeBSD.org Precedence: bulk I have a problem with popper. I installed FreeBSD on January 1995 and i try now to have a mail server, i tried popper, but it refuse to scrap files after a person had took his mail. I don't know what to do to repair this problem. I compiled with the stuff in ports-2.0 i think. Excuse my english but i am a french canadian. Thank for your respond Mario Verville From owner-freebsd-ports Wed Aug 23 16:53:05 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id QAA00943 for ports-outgoing; Wed, 23 Aug 1995 16:53:05 -0700 Received: from eikon.e-technik.tu-muenchen.de (eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id QAA00934 for ; Wed, 23 Aug 1995 16:53:00 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id BAA15454; Thu, 24 Aug 1995 01:52:39 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id BAA06348; Thu, 24 Aug 1995 01:48:31 +0200 Message-Id: <199508232348.BAA06348@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: asami@cs.berkeley.edu cc: ports@freebsd.org, msmith@atrad.adelaide.edu.au, phil@gmrs.isar.de Subject: Re: pbasic-2.0-950813.tar.gz + pbasic-2.0-950813.src.tar.gz uploaded Date: Thu, 24 Aug 1995 01:48:30 +0200 From: "Julian Stacey " Sender: ports-owner@freebsd.org Precedence: bulk Ports Readers: My request for comment on the draft pbasic port is now _Terminated_ Satoshi, As you generated much more email for me than I could possibly want, I now hand the job over to you in entirety: You are now responsible for commiting a ports wrapper, & maintaining Phil Cockroft's Basic on FreeBSD. If you refuse, I am prepared to commit a tree alone, unaided, & without further input from _anyone_. I am also prepared to commit nothing if the ports@freebsd group prefers that. I am not prepared to be micro-managed, or to spend further time on this little ports wrapper, the efficient way forward is for one person to commit something, without further fuss & comment, it can be fiddled with later as required. I require a straight decision : Do you accept this job ? (with MAINTAINER = asami in the Makefile) Do you refuse it ? Do you nominate a 3rd person ? Do you agree I have carte-blanche for an inital commit ? (with MAINTAINER = jhs ) I will delete my freefall:~jhs/pbasic* sources if I don't get a simple answer. I get a prevaricating answer. I provided the ports wrapper for purely altruistic reasons: - Phil's a friend - I'm involved with FreeBSD - Some guy on ports@ asked for a Basic, I don't even Want basic myself, it's to provide choice for our user base, not me. My interest & enthusiasm is now exhausted. I await your commits of Phil's Basic to the ports/lang/ code tree. Julian S jhs@freebsd.org From owner-freebsd-ports Wed Aug 23 18:51:46 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id SAA05340 for ports-outgoing; Wed, 23 Aug 1995 18:51:46 -0700 Received: from forgery.CS.Berkeley.EDU (forgery.CS.Berkeley.EDU [128.32.33.75]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id SAA05334 for ; Wed, 23 Aug 1995 18:51:45 -0700 Received: (from asami@localhost) by forgery.CS.Berkeley.EDU (8.6.11/8.6.9) id SAA03827; Wed, 23 Aug 1995 18:50:12 -0700 Date: Wed, 23 Aug 1995 18:50:12 -0700 Message-Id: <199508240150.SAA03827@forgery.CS.Berkeley.EDU> To: jhs@vector.eikon.e-technik.tu-muenchen.de CC: ports@freebsd.org, msmith@atrad.adelaide.edu.au, phil@gmrs.isar.de In-reply-to: <199508232348.BAA06348@vector.eikon.e-technik.tu-muenchen.de> (jhs@vector.eikon.e-technik.tu-muenchen.de) Subject: Re: pbasic-2.0-950813.tar.gz + pbasic-2.0-950813.src.tar.gz uploaded From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * I now hand the job over to you in entirety: * You are now responsible for commiting a ports wrapper, * & maintaining Phil Cockroft's Basic on FreeBSD. Ok, that's fine for me! Just committed! Send me updates when he decides to release a new version, ok? :) Satoshi From owner-freebsd-ports Thu Aug 24 01:07:11 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id BAA03151 for ports-outgoing; Thu, 24 Aug 1995 01:07:11 -0700 Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.RWTH-Aachen.DE [134.130.90.6]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id BAA03092 for ; Thu, 24 Aug 1995 01:06:48 -0700 Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.6.11/8.6.9) id KAA11024 for ports@freebsd.org; Thu, 24 Aug 1995 10:06:00 +0200 From: Thomas Gellekum Message-Id: <199508240806.KAA11024@ghpc6.ihf.rwth-aachen.de> Subject: tk4, tcl74 test results To: ports@freebsd.org Date: Thu, 24 Aug 1995 10:05:59 +0200 (MET DST) Organization: Institut f. Hochfrequenztechnik, RWTH Aachen X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 251 Sender: ports-owner@freebsd.org Precedence: bulk Moin moin, After compiling tcl74 and tk4 I ran the tests for both. I keep getting the domain error in expr.test for tcl74, but more importantly, tk4 gives a load of error messages in entry.test and focus.test. Can someone please look after this? tg From owner-freebsd-ports Thu Aug 24 07:03:40 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id HAA20881 for ports-outgoing; Thu, 24 Aug 1995 07:03:40 -0700 Received: from eikon.e-technik.tu-muenchen.de (eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id HAA20874 for ; Thu, 24 Aug 1995 07:03:36 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id PAA26593; Thu, 24 Aug 1995 15:50:00 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id PAA03112; Thu, 24 Aug 1995 15:49:51 +0200 Message-Id: <199508241349.PAA03112@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: asami@cs.berkeley.edu (Satoshi Asami) cc: ports@freebsd.org, msmith@atrad.adelaide.edu.au, phil@gmrs.isar.de Subject: Re: pbasic-2.0-950813.tar.gz + pbasic-2.0-950813.src.tar.gz uploaded In-reply-to: Your message of "Wed, 23 Aug 1995 18:50:12 PDT." <199508240150.SAA03827@forgery.CS.Berkeley.EDU> Date: Thu, 24 Aug 1995 15:49:51 +0200 From: "Julian Stacey " Sender: ports-owner@freebsd.org Precedence: bulk Re. Phil Cockroft's Basic > Ok, that's fine for me! Just committed! > Send me updates when he decides to release a new version, ok? :) Will do. Julian S From owner-freebsd-ports Thu Aug 24 17:52:50 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id RAA14071 for ports-outgoing; Thu, 24 Aug 1995 17:52:50 -0700 Received: from Wit401402.student.utwente.nl (Wit401402.student.utwente.nl [130.89.236.162]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id RAA14065 for ; Thu, 24 Aug 1995 17:52:48 -0700 Received: (from alain@localhost) by Wit401402.student.utwente.nl (8.6.12/8.6.9) id CAA13496; Fri, 25 Aug 1995 02:49:30 +0200 Date: Fri, 25 Aug 1995 02:49:30 +0200 (MET DST) From: Alain Kalker Reply-To: A.C.P.M.Kalker@student.utwente.nl To: Satoshi Asami cc: ports@freebsd.org Subject: New port for slirp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ports-owner@freebsd.org Precedence: bulk Dear Satoshi, When I wanted to install SLiRP on my box from the ports directory, was I surprised to find out that it wasn't SLiRP but SLuRP that finally appeared! So I thought that there had to be a newer one. So I found it (v0.95f) and thought it a good way to get a gentle start in the porting practice. I hope I am not bypassing the regular maintainer (Jordan?) with this, but I needed SLiRP badly, and I hope I do others a service. Please have a look at it, I have uploaded my 'port' (well, it almost compiles straight out of the box, only the install kludge had to remain) and the original distribution tarball to ftp.freebsd.org Grtns, Alain From owner-freebsd-ports Fri Aug 25 00:12:20 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA04260 for ports-outgoing; Fri, 25 Aug 1995 00:12:20 -0700 Received: from web.azstarnet.com (azstarnet.com [169.197.1.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA04245 ; Fri, 25 Aug 1995 00:12:17 -0700 Received: from dialup87.azstarnet.com (dialup87.azstarnet.com [169.197.2.87]) by web.azstarnet.com (8.6.10/8.6.10) with SMTP id AAA28407; Fri, 25 Aug 1995 00:11:24 -0700 Date: Fri, 25 Aug 1995 00:11:24 -0700 Message-Id: <199508250711.AAA28407@web.azstarnet.com> X-Sender: maher@azstarnet.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: questions@FreeBSD.org, ports@FreeBSD.org, FreeBSD-hackers@freefall.FreeBSD.org, FreeBSD-FAQ@freefall.FreeBSD.org From: maher@azstarnet.com (maher katbah) Subject: cu on BSD Sender: ports-owner@FreeBSD.org Precedence: bulk Hi I have freeBSD on my machine, and I connect to internet provider through a modem by using cu. The provider is using sun solries in his machine. Now when I am trying to download a 2.97 MB file by using the ~t , or ~take I will receive 2.93MB file. After that if I want to gunzip it , I have "corrupt file" message. From owner-freebsd-ports Fri Aug 25 03:44:45 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id DAA25079 for ports-outgoing; Fri, 25 Aug 1995 03:44:45 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id DAA25073 for ; Fri, 25 Aug 1995 03:44:44 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id DAA04307; Fri, 25 Aug 1995 03:44:07 -0700 Date: Fri, 25 Aug 1995 03:44:07 -0700 Message-Id: <199508251044.DAA04307@silvia.HIP.Berkeley.EDU> To: JKOKOT@demeter.ipan.lublin.pl CC: ports@freebsd.org In-reply-to: <19AE965E82@demeter.ipan.lublin.pl> (JKOKOT@demeter.ipan.lublin.pl) Subject: Re: Chipmunk port From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * Date: Tue, 1 Aug 1995 12:12:37 CET (Boy, is my mail queue long or what?!?) * I uploaded chipmunk.tgz to freebsd.cdrom.com/pub/FreeBSD/incoming/ * This is an electronic CAD Thanks, committed (after some changes)! Satoshi From owner-freebsd-ports Fri Aug 25 06:00:13 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id GAA01303 for ports-outgoing; Fri, 25 Aug 1995 06:00:13 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id GAA01275 for ; Fri, 25 Aug 1995 06:00:08 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id NAA16555 for ports@freebsd.org; Fri, 25 Aug 1995 13:59:56 +0100 From: Paul Richards Message-Id: <199508251259.NAA16555@server.netcraft.co.uk> Subject: msql To: ports@freebsd.org Date: Fri, 25 Aug 1995 13:59:56 +0100 (BST) Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 806 Sender: ports-owner@freebsd.org Precedence: bulk The license on msql looks unacceptable for the cdrom. "Commercial purposes" is defined within the scope of this license as the generation of monetary revenue from the redistribution of the software or modified versions of the software, beit by itself or "bundled" with or incorporated into any other product. Generation of revenue via the use of this software is not considered a "commercial purpose". I also ran into a little quirk in that mtree doesn't build the top level directory for the package and if I change that tope-level directory during configuration then mtree still looks for the default location. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home) From owner-freebsd-ports Fri Aug 25 06:00:54 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id GAA01383 for ports-outgoing; Fri, 25 Aug 1995 06:00:54 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id GAA01376 for ; Fri, 25 Aug 1995 06:00:51 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id OAA16567 for ports@freebsd.org; Fri, 25 Aug 1995 14:00:40 +0100 From: Paul Richards Message-Id: <199508251300.OAA16567@server.netcraft.co.uk> Subject: Dependencies To: ports@freebsd.org Date: Fri, 25 Aug 1995 14:00:39 +0100 (BST) Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 543 Sender: ports-owner@freebsd.org Precedence: bulk I don't like the way dependencies currently work. I want to build ghostview but it depends on ghostscript so when I try and compile it it first goes off to get ghostscript and builds that, but I've already got ghostscript installed! Can't the dependencies use pkg_* in some way to see if the package already exists before trying to rebuild it again? -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home) From owner-freebsd-ports Fri Aug 25 07:38:10 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id HAA05219 for ports-outgoing; Fri, 25 Aug 1995 07:38:10 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id HAA05209 for ; Fri, 25 Aug 1995 07:38:07 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id HAA22314; Fri, 25 Aug 1995 07:35:28 -0700 To: A.C.P.M.Kalker@student.utwente.nl cc: Satoshi Asami , ports@freebsd.org Subject: Re: New port for slirp In-reply-to: Your message of "Fri, 25 Aug 1995 02:49:30 +0200." Date: Fri, 25 Aug 1995 07:35:27 -0700 Message-ID: <22311.809361327@time.cdrom.com> From: "Jordan K. Hubbard" Sender: ports-owner@freebsd.org Precedence: bulk I don't mind at all! Go right ahead and update it.. > > Dear Satoshi, > > When I wanted to install SLiRP on my box from the ports directory, was I > surprised to find out that it wasn't SLiRP but SLuRP that finally appeared! > > So I thought that there had to be a newer one. So I found it (v0.95f) and > thought it a good way to get a gentle start in the porting practice. I > hope I am not bypassing the regular maintainer (Jordan?) with this, > but I needed SLiRP badly, and I hope I do others a service. > > Please have a look at it, I have uploaded my 'port' (well, it > almost compiles straight out of the box, only the install kludge had to > remain) and the original distribution tarball to ftp.freebsd.org > > Grtns, > > Alain From owner-freebsd-ports Fri Aug 25 08:51:40 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id IAA10100 for ports-outgoing; Fri, 25 Aug 1995 08:51:40 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id IAA10072 ; Fri, 25 Aug 1995 08:51:36 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id IAA22499; Fri, 25 Aug 1995 08:51:25 -0700 To: maher@azstarnet.com (maher katbah) cc: questions@FreeBSD.org, ports@FreeBSD.org, FreeBSD-hackers@freefall.FreeBSD.org, FreeBSD-FAQ@freefall.FreeBSD.org Followup-to: questions@freebsd.org Subject: Re: cu on BSD In-reply-to: Your message of "Fri, 25 Aug 1995 00:11:24 PDT." <199508250711.AAA28407@web.azstarnet.com> Date: Fri, 25 Aug 1995 08:51:25 -0700 Message-ID: <22497.809365885@time.cdrom.com> From: "Jordan K. Hubbard" Sender: ports-owner@FreeBSD.org Precedence: bulk > I have freeBSD on my machine, and I connect to internet provider through a I'd like to ask everyone to let this question drop. I don't know what it is with this guy, but he's totally ignored my previous two pleas to STOP cross-posting his messages to every list we own! I have asked him nicely, I have asked him more firmly, but still the spam. I figure he'll go away if we simply ignore him completely or maybe he'll get the message that if he wants to talk to us, he shouldn't shout! Either way, I figure he's just lost his free Q&A privileges until he's at least willing to respond to one of my messages asking him to stop! Thanks. Jordan From owner-freebsd-ports Fri Aug 25 12:41:13 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id MAA26133 for ports-outgoing; Fri, 25 Aug 1995 12:41:13 -0700 Received: from oasis.txdirect.net (oasis.txdirect.net [204.57.120.34]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id MAA26126 for ; Fri, 25 Aug 1995 12:41:05 -0700 Received: (from rsnow@localhost) by oasis.txdirect.net (8.6.11/8.6.9) id OAA06659; Fri, 25 Aug 1995 14:40:17 -0500 Date: Fri, 25 Aug 1995 14:40:01 -0500 (CDT) From: Rob Snow X-Sender: rsnow@oasis To: "Ports@FreeBSD.org" Subject: popclient port in incoming Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ports-owner@freebsd.org Precedence: bulk I've put the popclient-2.21 port into incoming on freebsd.cdrom.com. It is called popclient.port.tgz. Popclient is a pop2 and pop3 client for retrieving mail from a pop server. --- Rob Snow rsnow@txdirect.net From owner-freebsd-ports Fri Aug 25 15:50:42 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id PAA07045 for ports-outgoing; Fri, 25 Aug 1995 15:50:42 -0700 Received: from tserv.lodgenet.com (dial5.iw.net [204.157.148.54]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id PAA06717 for ; Fri, 25 Aug 1995 15:49:16 -0700 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id RAA24957 for ; Fri, 25 Aug 1995 17:49:28 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.6.11/8.6.9) with SMTP id RAA19452 for ; Fri, 25 Aug 1995 17:55:07 -0500 Message-Id: <199508252255.RAA19452@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: ports@freebsd.org Subject: apache port Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="===_0_Fri_Aug_25_17:54:53_CDT_1995" Date: Fri, 25 Aug 1995 17:55:07 -0500 From: "Eric L. Hernes" Sender: ports-owner@freebsd.org Precedence: bulk This is a multipart MIME message. --===_0_Fri_Aug_25_17:54:53_CDT_1995 Content-Type: text/plain; charset=us-ascii Here's a port of the apache httpd. All that's missing is the knob in /etc/sysconfig and a homepage. eric. --===_0_Fri_Aug_25_17:54:53_CDT_1995 Content-Type: text/plain; charset=us-ascii Content-Description: apache-port.tgz Content-Transfer-Encoding: x-uuencode begin 644 apache-port.tgz M'XL(```````"`^T;_6_:2C*_EK]BKHW4-@6#C2&$N[XK#:1%CX0HD&LK/2E: M[`4L;"^W:R?EJO9OO]E=&QP@29_NDK1]'B4!S\Y^S=?.[#AD3IPI+>_<)X!= MV:_58`<0JO7KGQHJ`/6*N6_7S$JE!F!6:K7]':CM/`#$(B(<8(=RSYG>0G=7 M^T\*1,O_F,SHV//IO&P MH/`,*7>[[BY^*;2[@^%)Z[CS^HE>UT7%4`LX_?U=%EU*T(>M8>==_ZS;&;QZ M_03'*QRW!L/.V<6@.^P,7C\91_-FN8Q_#2)P+A(8Q#'B67D>C\H?/GPH)S92 M*!A>Z/BQ2^$?(^$:DFE&,/NM\`O8OY2U*#^V_Z_N6V:MCO9OUO>MW/\_N/P# MM_88_A_VZVORMZJVE?O_AX#C=@U>7'.B!O+#F/SG);R&QLBJFE;%&M4:EFF. M#ZS1`7%JC49U1)Q&S2:%G1Q^#?N?SR;WEP-\?_Q?K58K5>G_J[:9^_\'EG^[ M,S@\>P3_;U9L>RE_LZ[\/R8`N?]_"("[H*4#_UMITIP`#Q`\3$(7XOG+0N'# ME$3@"?"B?Q9**R@4])"RB83P?C@\!4'Y)>7@4N%-0NH"P2:8^_&DY,E,8^X3 MAP8TC&0Z`A'V/3D(*+ M"9?]TUEQP84DL!>8^(0+&,OD!J?S%RK-H0*S&0@Q3QIC8A-S*HJR$TR)VD'K MM`M74]2.`O%]=B4W#!&#$07Z.:*ABWWQ,:`T@ABG%,]Q*.KB5(PC"1&>OS`P MI6%.++=(9/Z5Y9?BF.^K9;M9(LE`%I9\+Z3XJ=HQ6RG"I4?4P_E9KS"-5&YS M=75E:$LW&)^D"8WB5H9BNIA3CKF;+_.ME`@%F9^2?XGS_[!_?-PY&3Y"_&^; M2_^/D;_T_[9EYO[_(2#QQ3KTAU)).C3I$A+GF!O_7\?^3WO=P?`^YK@K_JM6 MD_S?MBO5NK[_K==R^W\(P'._[$R\TL@+"_*[-ONRSR8B^RQ=@IM%."P<:ZPA MOVXT"1YL;R".0X78WA9X`34BC$+TW!XB17E$G)DQ\<99E!<2OMA$3NGG=:1/ MPHW>G,UHN(Z,N8C61W$2BC%=IXS#62O/DN$/.#YC\?__C+^WZ]7*A*U7ZWGY_]#P-[>'AAX6COE0SR! MO4G,U=W"MR?9FJW9M*M-NZ'KM25,$K;T>'*]R&M5FF9-=]B[#O(9[(,B>@3U M"/`,!IWAL'OR;@!'_3,8ON_`X--@V#F&HU[KW<"`[A%\ZI]#NW_R?%B$MZTV MTBCR#]U>#]ZW3D\[)P8.I,8Z8AP&<=@?@%WX&[3./UX0ZD].#_I#^P5 M&?,)]P18AD*MT?9[K;/NP%)-G8_#L]9%K_M6-OF".3,:X9=0^(H?>COJKN9^ MM_/L_O>S35P'E>)!8RFNZ^.V3ON]7G^YAA,:O1VTRT><4OF)OUU'K_]XNOOE]*QSU/WXM9P)M_]XBF3M_N&YO/&YZ/4/6\-N_V2#^H^G=_+[ M$=B]34/-:KUHVM;*I2#;Y&HQ-I>,\T)U+3KG[/-B:5K)X*[O7@3ZJP3\>H$H M@TEE6BV`S3PJ4CI)DZ"0+K54S$I\?U&$:"IOO>45]E[F[GI/75[+GIA<8>\@ M0&FJ>V/=7<1S_1H.@1Z;H)X$)`+,"^0;.91`S$G#K>>(%M)%)* MF')AZ8G^+USX>7BP.LUT:CI=/\=J5K-RL'Z.);2;I';EYA-LWRPV*EK=Y$CR MT4[Y7MZ#-AW+>WG%!ET,4/?W=$QB/THK#U,64+D]`UKA`DE11#Z)L$%5*3PA MJR[(,OD>UI47X41))]=O;@5$IZ68R&S?H?X91HE+'DJ!Z"ABYF4$B]NZXRQ"-@XW<"U.3;< M26:JC;;M,^)?ESEBR\3'Y+,A2SDCG%7-[\3'1./8H*JS$2TW+NL<,VESS=P MPYIR5M+X*#>*5L5495!.3'$*RI68M8A6X=O] MBX@CK]XH-LG]/I*`5O'`#RVAC/6FMXI_PG:O==FTW.HM+MZTBN8JZET67X4! M;Q>I*R_*XRBM$@O%^8C,O68CS$U6\1NV3AY;FQ[(+1JH$OLGVE!.R/[9Z]%*JOPI- M%#.7-O8S,1/MY''YMU4YS4;1M`Y6ZMG2>VX"&C`H-T62UQE2;A`=-*D`_H6R MWU":7>!%+PVUH;$.N'#NU8@PEA*0.Y5O!L@OFEFZ,;EOW:YZNFWIW!SNS2/5 MK:E]A;P>Y\P7"&[+K`XD@WK6T569_95A#B44:]\E252 M#)>QK(K[9!236$HBV:6M_"B27=VO_]`RO9_.=!I>KXK5RC=I!>*"#VN>M2O M>:EN^(/89A,_GS@N8(KT=UQ<>MM'L^C=+\>MWSM?8?>-[I>,J/N6@ADR"TIS MV'8'<1N%TK+;"-*2Y9VSJ"#@.\A4P1/)=K]T3P;#5J_W%4H.E`24`I#%BQ)3 M,1LL\\4;][0V0@#R[AN[AVS$W`5L2RAN7GFVQ/J=8U\+>&X9>5FA_6<3/UX;N'U9YJ[P;-RDN#.>200PXYY)!##CGDD$,..>20 40PXYY)!##CG\RO!?M^\4XP!0``!J ` end --===_0_Fri_Aug_25_17:54:53_CDT_1995 Content-Type: text/plain; charset=us-ascii -- erich@lodgenet.com erich@rrnet.com --===_0_Fri_Aug_25_17:54:53_CDT_1995-- From owner-freebsd-ports Fri Aug 25 15:52:47 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id PAA07636 for ports-outgoing; Fri, 25 Aug 1995 15:52:47 -0700 Received: from tserv.lodgenet.com (dial5.iw.net [204.157.148.54]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id PAA07257 for ; Fri, 25 Aug 1995 15:51:21 -0700 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id RAA24965 for ; Fri, 25 Aug 1995 17:51:34 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.6.11/8.6.9) with SMTP id RAA19485 for ; Fri, 25 Aug 1995 17:57:15 -0500 Message-Id: <199508252257.RAA19485@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: ports@freebsd.org Subject: port for xaero, a povray modeler Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="===_0_Fri_Aug_25_17:56:59_CDT_1995" Date: Fri, 25 Aug 1995 17:57:14 -0500 From: "Eric L. Hernes" Sender: ports-owner@freebsd.org Precedence: bulk This is a multipart MIME message. --===_0_Fri_Aug_25_17:56:59_CDT_1995 Content-Type: text/plain; charset=us-ascii Since I've never gotten povray to display anything useful by hand, I found this modeller, which seems to help. There could be a strong argument for making EXEC_DEPENDS=netpbm. eric. --===_0_Fri_Aug_25_17:56:59_CDT_1995 Content-Type: text/plain; charset=us-ascii Content-Description: aero-port.tgz Content-Transfer-Encoding: x-uuencode begin 644 aero-port.tgz M'XL(```````"`^U:;7/B.!+.5_PK^I)433()MF4;2+AC:PDX,]R&A`)F)WN[ M6Y2Q!;AB8Z]M0G+[\MNO)6-(@,SD<@.YW=%38&RIU6IW2RUU"XM&@;*S68"A ME@H%V`&$7GS\FT(%**JD9!1(H4``B*J5M!TH[&P!DSBQ(H`=&KGVZ!-TGZO_ MD\)B]F]:-W3@>G1#?1!5+1K&D_8G*C%2^Q.BZ;J.)9I*]!U0A?TWCCVXI%,( M@RB)P0X\C]J)&XS!GXT(&`11F1F)C1-I#[ZG4!G)X6L-''4>`OB#-P=7\;16.: MR';@2WM(N=]P]O%&JC-2&5W#V-I8_M[SKM6B67FP;134K`A),N&F>] MNMDR+^N="GO%P710WO^U==7N=NJ-]N\*"J>1IG23)[MCV)@Z%?_1C1V;&E_V;;Z0=@:\.?'BRF1YO;A?P M[/5?+1D(]"=$+Q7%^K]E^_O.AA3^F?4?H%1:LK^F&B6Q_F\#S7H!#AXOHS(J M1![^^Q`J8*L&<8I$UXR2T2<6M=33DQ.M0$].3PU2TBRQ9/PEYG]X,]QD#/AL M_T_4@EXL,/^O%D3\MUW[U\U.K?U*\9]66MB_P.(_]"W"_V\%1U\.TM$1/(7K MJMF^@K99K3?-65$.`;S5EY-`Z@88FHX=&D$RHC"-W"2A&*U:]TEDV5C*=SK' MT+KZOEW]@<@J!!&,Z11KXE$P\1SH4VD24T>&+K:?A4D.Q';DADG:FH7$8$V2 MP+<2UX8A'=/(XD%S,,#.+U0*73N91'36))@DK);)M"0+]H[\6<5N,K22 M(`S]70S$?=\:.]*#9JVSYA$X;IQ$;G_">I.A"G%(;=?R(*%WJ7!@6QB6.E*J M:'G1%[T+/-3O=U M]O^ZOLC_8NC'_;]N"/^_#?3=L7+'DWOL+@QNXTD_3O@#.@;;HU:4/:!+NL_N MF=*2!P^)Y+E]Y9H0Q0K#O$,'UL1+8N6ZRCAG5;P?GA!#UZFQ)-2:JI!@)2K; M\N*G*();\G15RENFDWSLOL:\Q^*9+[_,S1V_J,131/S?UOV3_/W MD,^#&X,U!IQ3T+=P%P0\S\VV*KCEF26/Q93Y"\Y_*[%'F\L`/__\URCJI)C& M?X:(_[=N?_Z;MZSM^G\T^WS_IQ9*S/ZZH0O_OQ6\??L6LN/_/W+=T20]JC6` MJ&6BE8F:'M/F<7'(R):I^($NIWK[&.P9-'*LG0!_!-B##DT`A]D(IB.*X?%] M,(&I-4Y83(KA:8+A*_#M'*Y##K@)QJ>XH?1=@M!>-,WZ_?I0S$N2[8"C+ M"GZPB']GW%(BY)1;)D`6\O[!^ZM.M_M#RSQD';::RX1WH9_79<-:H=[4I$EM M.Y\TS[;M_YMA&4GQLR9-J=8:$_8^:\^\-Y@.4,1GVS7O78?^0\9;->^ZJ7RJ M'9^>9E.9NS_T+`=FO=&]0K_VS\XA/E4O_V4VWIG9XWGG#-^&_8&(B9G;/ZC5 M6'&G6^TV^%W=//OP[A#RP9F M#;@94+?6E%W]";LF[,+RO:G.\8K16M[+Q$=6GL^,GMO,J*5WEA]Z65[[0?+[ M(`C9K^4=\NG&]#]?H[XR_7>:>&G4S-04KV:&==."D)-C@OLV7L#LQ`OTN:7P M8P?A_3ECVPWJ-$[<,6=<+L]LTCJ<:S_;(QQ*1Y!C)Q/AP\)96A&K?H2\D]6P M'<$A_`R__0;^C>-&D`\?52WH5_8,:;=+3==3+61%?[2:D5SI<4Z;'O3$\T3H M\ENN$&9)TN<0\J3I,PE7Z%@ZYDU<[O5X:8_]F;!5[;[O].Z8@A4-V3Y^.F*GE#_"_A[D MAPFH\//?P0E23\2%F/FAEPL!1Q>K<^3EDHD,H8"`@("`@("`@("`@("`@("` 8@("`@("`@("`@(#`GP'_`>3-T(<`4``` ` end --===_0_Fri_Aug_25_17:56:59_CDT_1995 Content-Type: text/plain; charset=us-ascii -- erich@lodgenet.com erich@rrnet.com --===_0_Fri_Aug_25_17:56:59_CDT_1995-- From owner-freebsd-ports Fri Aug 25 17:27:41 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id RAA11492 for ports-outgoing; Fri, 25 Aug 1995 17:27:41 -0700 Received: from wildcat.cs.dartmouth.edu (wildcat.cs.dartmouth.edu [129.170.200.34]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id RAA11482 for ; Fri, 25 Aug 1995 17:27:39 -0700 Received: by wildcat.cs.dartmouth.edu (8.6.10/4.2) id UAA24650; Fri, 25 Aug 1995 20:26:38 -0400 Date: Fri, 25 Aug 1995 20:26:38 -0400 From: dfk@wildcat.cs.dartmouth.edu (David Kotz) Message-Id: <199508260026.UAA24650@wildcat.cs.dartmouth.edu> To: ports@freebsd.org Subject: INDEX in FreeBSD/ports-2.0/ Sender: ports-owner@freebsd.org Precedence: bulk The INDEX file in ftp://ftp.freebsd.org/pub/FreeBSD/ports-2.0/ is out of date. Could you please update it? dave From owner-freebsd-ports Fri Aug 25 18:19:00 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id SAA12796 for ports-outgoing; Fri, 25 Aug 1995 18:19:00 -0700 Received: from Wit401402.student.utwente.nl (Wit401402.student.utwente.nl [130.89.236.162]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id SAA12790 for ; Fri, 25 Aug 1995 18:18:57 -0700 Received: (from alain@localhost) by Wit401402.student.utwente.nl (8.6.12/8.6.9) id DAA00644; Sat, 26 Aug 1995 03:18:21 +0200 Date: Sat, 26 Aug 1995 03:18:21 +0200 (MET DST) From: Alain Kalker Reply-To: A.C.P.M.Kalker@student.utwente.nl To: "Jordan K. Hubbard" cc: Satoshi Asami , ports@freebsd.org Subject: Re: New port for slirp In-Reply-To: <22311.809361327@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ports-owner@freebsd.org Precedence: bulk On Fri, 25 Aug 1995, Jordan K. Hubbard wrote: > I don't mind at all! Go right ahead and update it.. > Thanks! Some things I forgot to add in my original message: - configure says there is an option to not compile ppp support into the program. I don't know if this is sufficient reason to make the port interactive to ask the user about it, so I left it as it is. - The second URL in the documentation (ftp://freedom.wit.com:...) seems to be no longer valid (directory does not exist anymore). Hope this is of some use to you. --- Alain From owner-freebsd-ports Fri Aug 25 22:18:05 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id WAA20047 for ports-outgoing; Fri, 25 Aug 1995 22:18:05 -0700 Received: from idiom.com (idiom.com [140.174.82.4]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id WAA20039 for ; Fri, 25 Aug 1995 22:17:48 -0700 Received: (from muir@localhost) by idiom.com (8.6.11/8.6.10) id WAA16415; Fri, 25 Aug 1995 22:17:27 -0700 Date: Fri, 25 Aug 1995 22:17:27 -0700 From: David Muir Sharnoff Message-Id: <199508260517.WAA16415@idiom.com> To: agc@uts.amdahl.com Subject: Re: Postgres95 for FreeBSD Cc: ports@freebsd.org Sender: ports-owner@freebsd.org Precedence: bulk * I'm sure there are others that I've missed. Ummm, many. I haven't updated this in way too long, but ... Have fun! If you're wondering which ones might be useful, I'm not sure. I would certianly give Exodus a try. Also, qddb, arjuna, obst, and yooda. Of the dbm clones, it would be nice to support gdbm. Tdbm would be really nice, but it might be a fair bit of work. -Dave >From free-databases@idiom.com Mon Mar 20 20:34:00 PST 1995 Article: 17182 of comp.databases Path: idiom.com!idiom.com!not-for-mail From: David Muir Sharnoff Newsgroups: comp.databases,comp.databases.object,comp.answers,news.answers Subject: Catalog of free database systems Supersedes: Message-ID: Followup-To: comp.databases Reply-To: free-databases@idiom.com Date: 21 Mar 95 04:31:06 GMT Expires: Fri, 15 Sep 1995 23:59:00 GMT Approved: news-answers-request@mit.edu Organization: Idiom Consulting Lines: 2133 Xref: idiom.com comp.databases:17182 comp.databases.object:3522 comp.answers:9089 news.answers:26528 Archive-name: databases/free-databases Last-modified: 1995/03/20 Version: 1.14 Catalog of Free Database Systems This document attemts to catalog databases that are available without payment and with source. The latest version of the document can be ftp'ed: get pub/free-databases from ftp.idiom.com. The latest version is always posted; the ftp version is never ahead. There is a WWW version provided by Karl Guggisberg of the Software Composition Group: http://cuiwww.unige.ch/~scg/FreeDB/ I will post this document about once a month (ha!) to comp.databases, comp.databases.object, comp.answers, and news.answers. I will also post it to other groups somewhat randomly. Please send additions, corrections, and donations to David Muir Sharnoff I would like user testimonials. I want to know which databases are usable and which are trustable! Is there any database on this list that I could store payroll records on? Thanks, -Dave Idiom Consulting, Berkeley, CA Copyright (C) 1993-1995 David Muir Sharnoff, All rights reserved. --------------------------------------------------------------------------- Prototype entry: name: The name of the package version: The current version number of the package direct inquiries to "contact." interface from: (interface packages only) front end protocol/program/language interface to: (interface packages only) back end protocol/program/server/etc. interfaces: The external interfaces that are supported by the package. Common interfaces are: SQL, ESQL, dbm, X, etc. access methods: A list of the database access methods that are supported multiuser: Can more than one person access the package at the same time. transactions: Does the package support transactions? distributed: Does the package support distributed databases? query language: What query languages does the package support if any? SQL, QUEL, etc. index size: (full text packages only) the size of the index as a percentage of the size of the text to be indexed. limits: Any known, annoying limits robustness: Can this package be used on mission-critical data? Is the package bug free? Does it crash? If it supports multi-user transactions, does it make guarentees and keep them? description: A description of the package. references: Pointers to other documentation (not including that which is included in the package) status: current developement status (supported, actively developed, etc) announcements: Where to get announcements discussion: Where to send, or how to join discussions about the package bugs: Where to send bug reports requires: Special requirements for installing or running ports: What does the package run on? restrictions: Special copyright or other restrictions on the software author: The primary author, if known. If not known, contact: The current contact point. If not specified, use "author." how to get: Instructions for obtaining the package updated: When the package was last updated (yyyy/mm/dd) --------------------------------------------------------------------------- Selected changes: new listings: ChezSybase - a ShezScheme/Sybase interface updates: Arjuna 3.2 is available CORAL 1.2 is available mSQL 1.0.5 is available PQL 0.8 is available removed entry Essense -- now part of Harvest --------------------------------------------------------------------------- --------------------------- relational databases -------------------------- --------------------------------------------------------------------------- name: DiamondBase version: 0.31 interfaces: C++ library access methods: b+ tree multiuser: Beta in this version transactions: no distributed: no query language: C++ methods limits: limits are set at compile time. The default max records is 21474836. robustness: The database engine is quite stable. The multi user component is a more recent addition, and is still considered beta. The single user version is separate however and unaffected. description: DiamondBase is written entirely in C++, and uses a schema compiler to generate C++ class defintions for the objects, as well as some comparison code which is also linked in to the final executable. Facilities are now available to access generic relations without providing comparison code. It was written originally as a replacement for MetalBase which was too slow. DiamondBase is very fast. announcements: send mail to Darren Platt to be put on their list questions: send mail to Darren Platt bugs: send mail to Darren Platt requires: C++ ports: many Unix platforms and OS/2 under cfront or gcc or Borland's compiler. Recent ports to Dos/windows. restrictions: Free usage for non-commerical applications -- negotiate anything else. author: Kevin Lentin, Andrew Davison, Darren Platt contact: Darren Platt how to get: ftp pub/export/diamond.tar.gz from ftp.cs.monash.edu.au updated: 1994/12/22 name: PQL version: 0.8 interfaces: interactive, stdin and shell mode access methods: hash multiuser: no transactions: yes distributed: no query language: SQL subset limits: ? robustness: Early phase of release, still many bgs description: PQL stands for "plain query language" and is a kind of SQL (rather a subset) Nearly all features of SQL are supported, like joins, subqueries and grouping. The join operation has been optimized using a iterative "select and join" algorithm which runs over all joined base tables. In addition to the PQL-Interpreter, a relational and transaction oriented database engin e interface is shipped with the package. The engine is based on the lower level GDBM interface, a freely available database library. bugs: author requires: gdbm, GNU readline ports: unix author: Bjoern Lemke how to get: ftp pub/unix/database from info2.rus.uni-stuttgart.de updated: 1992/03/01 name: Qddb version: 1.41.9 patch 4 interfaces: query language, Tcl/Tk access methods: ? multiuser: yes transactions: ? distributed: no query language: supports regular expressions; words, numbers, and dates; and ranges of words, numbers, and dates. limits: ? robustness: This is BETA software, but we have been happily using the underlying stuff for years. description: QDDB stands for 'Quick and Dirty DataBase'. Qddb is a database suite that allows you to create relations, add tuples, modify tuples, delete tuples, and search for tuples in a fast and very flexible way. Qddb 1.40 can use Tcl as its configuration language, so you can build custom interfaces to your Qddb databases with it. We provide a reasonably nice generic interface so you can be up and running quickly. status: actively developed discussion: send "Subject: subscribe" with your address in the body to qddb-users-request@ms.uky.edu bugs: qddb-bugs@ms.uky.edu and qddb-users@ms.uky.edu requires: Tcl 7.3, Tk 3.6p1 ports: Ultrix, OSF/1, BSD/386, Linux, SunOS, Solaris. restrictions: GNU General Public License author: Eric H. Herrin II , Raphael Finkel how to get: ftp pub/unix/qddb/ from ftp.ms.uky.edu updated: 1995/02/03 name: Typhoon version: 1.06 interfaces: C API access methods: B-trees multiuser: Yes, but no locking mechanism at this point (will come soon) transactions: no distributed: no query language: none limits: A single file cannot exceed 4GB. robustness: The package is quite stable as it is shut down properly. It is currently used in a system that handles billing information (and some other applications). description: Typhoon is a relational database management system. It was originally inspired by Raima's db_VISTA (today Raima Data Manager) but is relational rather than network based. Typhoon lacks some of db_VISTA's features, but also contains a number of nice features not found in db_VISTA. All relations are defined in a so called Data Definition Language (ddl) file. You define the database relations like you would write a C structure with chars, ints, strings, multidimensional arrays, nested union and structures, etc. Then you define primary, alternate and foreign keys for each relation. The Data Definition Language Processor (ddlp) compiles the database defintion into a binary file which constitutes the database description. The database relations are accessed via C subroutines which manipulate individual records within a table. - Multiple open database - Multi-field keys - Nested structures in records - Controlled unions - Referential integrity - Variable length fields - Null keys (optional keys in db_VISTA, but easier to use) - Dynamic opening and closing of database files status: actively developed ports: SCO UNIX, Solaris, Tandem NonStop UNIX, AIX, Linux and OS/2. author: Thomas B. Pedersen how to get: comp.sources.misc volume 44; ftp pub/Linux/devel/db/typhoon-1.06.tar.gz from sunsite.unc.edu updated: 1994/10/03 name: University INGRES version: 8.9 interfaces: QUEL, EQUEL access methods: heap, hash, isam, ordered multiuser: yes transactions: yes, but no multistatement transactions. Each statement is ACID distributed: no query language: QUEL limits: ? robustness: Very mature technology description: This is the database program that was the basis for INGRES Corporation. Obviously, it does not have all the bells and whistles of the current commercial product. However, it is small and fast and it works. So called ordered relations are slow and not locked. references: "The INGRES Papers" Stonebraker ed. Addison Wesley ports: SunOS, Linux author: The Ingres project at UC Berkeley. contact: how to get: ftp pub/ingres/* from s2k-ftp.CS.Berkeley.EDU updated: 1993/05/20 name: MetalBase version: 5.0 interfaces: custome C library access methods: AVL-trees multiuser: yes, but in theory race conditions still exist transactions: yes distributed: no query language: "Report", and "View Relation" a curses based viewer limits: ? robustness: data corruption is possible when MetalBase is not shut down correctly description: MetalBase is a small relational database. It has all the pieces that a relational database should C interface, curses interface, report writer, etc. It does not have design which takes advantage of shared memory or the better access methods. None of the interfaces are standard, but all of them are easy to use. discussion: mbase-request@internode.com.au requires: curses ports: Linux, MS-DOS, Amiga, NeXT, Coherent, Macintosh MPW, SGI, Xenix restrictions: donations are suggested author: Richid Jernigan / PO Box 827 / Norris TN 37828 how to get: ftp systems/unix/linux/sources/usr.bin/mbase.tar.z from ftp.uu.net updated: 1992/10/01 name: mSQL (Mini SQL) version: 1.0.5 interfaces: C, ESL, Tcl, Perl, Python, NextSTEP adapter, Windows (WinSOCK) access methods: Flat data with external primary key mapped into virtual address space of server process. multiuser: yes (25 simultaneous connections) transactions: no distributed: no query language: SQL limits: none robustness: Pretty good - getting better all the time. One positive user testimonial so far. description: Mini SQL or mSQL is a light weight database engine that supports a significant subset of the ANSI SQL specification (including joins, ORDERing, DISTINCT, NULL handling, etc). It is a single proces engine and doesn't use vast amounts of system resources as other engines can. It supports client server operations over TCP/IP networks and provides quite reasonable performance. As an example, on a clunky old 25mhz 386 running Linux (one of the supported platforms) a sustained rate of 67 inserts per second was achieved during the insertion of 100,000 table entries. discussion: msql-list-request@Bond.edu.au ports: SunOS, Solaris, HP-UX, AIX, Linux, FreeBSD-2, SCO, SVR4, NeXT, Cray Unicos, OSF/1, Ultrix. restrictions: free for non-commercial use only author: David Hughes how to get: ftp pub/Minerva/msql/ from Bond.edu.au updated: 1995/02/15 name: Postgres version: 4.2 beta interfaces: libpq (C interface), pgbrowse (tk-based browser) access methods: Heap plus secondary indexes: B-tree, R-tree, Hash. multiuser: yes transactions: yes distributed: no query language: Postquel (incompatable, extended variant of QUEL) limits: ? robustness: The authors say: "It is not up to commercial levels of reliability. I would not want _my_ payroll records in it :-)" description: Postgres is a database research project under Prof. Michael Stonebraker at U. C. Berkeley. To facilitate research efforts, a software test-bed was created; this is the "Postgres" DBMS software. The Postgres DBMS is extended relational or object oriented, depending on the buzzword du jour. Postgres is relational. It is highly extensible. It has object oriented features like inheritance. it has query language procedures, rules, updatable views, and more. references: There are may papers available, both through ftp and as hard-copy technical reports. Cruse the ftp site for papers or mail Michelle Mattera discussion: send "Subject: ADD" to postgres-request@postgres.berkeley.edu linux: send "X-Mn-Admin: join postgres" to linux-activists-request@niksula.hut.fi bugs: ports: full support: Alpha OSF/1 1.3+, Mips Ultrix .2+, Sparc SunOS 4.1.1+, Power AIX 3.2.3+, HP-PA HP-UX 9.0+ comming soon: Sparc Solaris 2.3, i386 Linux previous versions: i386 SVR4, i386 386BSD, i386 Linux, i386 NextStep 3.1, NeXT NextStep 3.0, Sparc Solaris 2.1+, HP-PA HP-UX 8.07 contact: developers: admin: Michelle Mattera how to get: ftp pub/postgres/postgres-v4r2* from s2k-ftp.CS.Berkeley.EDU. pgbrowse: ftp pub/pgbrowse/* from crseo.ucsb.edu. updated: 1994/04/02 name: REQUIEM version: ? interfaces: RQL, ERQL (extension) access methods: B-tree indexes can be created on attributes of base relations. multiuser: yes (multiuser extension) transactions: yes (multiuser extension) distributed: no query language: RQL robustness: [seems to maintained by zero to few people --ed] description: REQUIEM (RElational Query and Update Interactive systEM) is an extensible, relational DBMS developed in C with a query language based on the relational algebra called RQL (Relational Query Language). There appears to be three versions of REQUIEM: the base version and two extensions. One extension adds multiuser capability. The other adds an embeddable version of the query langauge. references: "An Extensible DBMS for Small-Medium Scale Systems", Papazoglou, M.P., IEEE Micro, April 1989. Relational Database Management - A Systems Programming Approach, Papazoglou, M.P. and Valder, W., Prentice Hall International, UK, 1989. "The Development of a Program Interface for the RDBMS Requiem" Power, R.A., 1991 Honours Thesis (dvi file available with source code for the embedded version). ports: Sparc/SunOS; base version only: MS-DOS, Macintosh contact: (embedded version only) Robert Power how to get: ftp pub/requiem/REQUIEM.tar.Z (multiuser version) or pub/requiem/Requiem.tar.Z (embeddable version) from dcssoft.anu.edu.au The base version can be constructed from the multiuser version. updated: 1992/10/06 name: shql version: 1.3 Beta interfaces: SQL, shell multiuser: no transactions: no ? distributed: no limits: no NULLs in the data, spaces and backslashes may be added when the data contains punctuation, GROUP BY is not implemented. robustness: it is a shell script. description: Shql is a program that reads SQL commands interactively and executes those commands by creating and manipulating Unix files. The program is patterned after Ingres' interactive sql terminal monitor program. requires: bourne shell with functions, awk, grep, cut, sort, uniq, join, wc, and sed author: Bruce Momjian how to get: comp.sources.misc volumes 34, 41 and 42. Also ftp pub/net-sources/shql-patch-1.3-beta from ftp.idiom.com updated: 1994/08/06 --------------------------------------------------------------------------- --------------------------- object oriented ------------------------------- --------------------------------------------------------------------------- name: Arjuna Distributed Programming System version: 3.2 interfaces: C++ access methods: ? multiuser: yes transactions: yes, nested distributed: yes, includes replicated objects query language: ? limits: ? robustness: "all reported bugs fixed" description: Arjuna is a programming system for reliable distributed computing. Arjuna supports nested atomic actions for controlling operations on objects (instances of C++ classes), which can potentially be persistent. The software available includes a C++ stub generator which hides much of the details of client-server based programming, plus a system programmer's manual containing details of how to install Arjuna and use it to build fault-tolerant distributed applications. discussion: send "join arjuna YOUR-NAME-HERE" to mailbase@mailbase.ac.uk ports: UNIX: Suns, HPs, etc. restrictions: A commercial extension exists. contact: arjuna@newcastle.ac.uk how to get: ftp pub/Arjuna from arjuna.ncl.ac.uk updated: 1995/03/19 name: EXODUS Project software version: GNU E 2.3.3, Storage Manager (SM) 3.1 interfaces: GNU E, (C++ for direct access to the Storage Manager) access methods: B+tree and linear-hashing based indexes multiuser: yes, client-server transactions: yes, but not nested. distributed: yes, applications can access multiple servers in a single transaction. Distributed commits are performed across servers and clients have access to an interface allowing participation in distributed commits managed by an external agent. query language: GNU E -- a persistent programming language based on C++ robustness: High (at least for academic software). The SM release includes a facility for regression testing most features, including crash recovery. description: The EXODUS Storage Manager (SM) is a client-server object storage system which provides "storage objects" for storing data, versions of objects, "files" for grouping related storage objects, and indexes for supporting efficient object access. A storage object is an uninterpreted container of bytes which can range in size from a few bytes to hundreds of megabytes. The Storage Manager provides routines to read, overwrite, and efficiently grow and shrink objects. In addition, the Storage Manager provides transactions, lock-based concurrency control, and log-based recovery. GNU E is a persistent, object oriented programming language developed as part of the Exodus project. GNU E extends C++ with the notion of persistent data, program level data objects that can be transparently used across multiple executions of a program, or multiple programs, without explicit input and output operations. references: A bibliography of EXODUS related papers can be obtained from the ftp site described below. Some of the papers are available from the ftp server as technical reports, and are marked as such in the bibliography. status: No longer being developed. However, the authors are working on a new system, SHORE, and will support current Exodus users well enough to keep them going until SHORE is useable. GNU E 2.5.8 is in beta and can be ftped. discussion: Send "information exodus_all" to listproc@cs.wisc.edu to find out how to join the exodus_all mailing list. bugs: exodusbugs@cs.wisc.edu requires: g++ 2.3.3 (exactly 2.3.3. GNU E 2.5.8 is in beta) ports: MIPS/Ultrix, SPARC/SunOS, HP 7xx/HP-UX, Linux restrictions: none, but see copyright notice located in all source files author: The EXODUS Database Toolkit project at the University of Wisconsin contact: exodus@cs.wisc.edu how to get: ftp exodus/* from ftp.cs.wisc.edu updated: 1993/03/29 name: LINCKS (Linkoping Intelligent Communication of Knowledge System) version: 2.2.1 interfaces: C library, emacs-like editor/X11 access methods: ? multiuser: yes transactions: no distributed: no, but maybe later query language: hypertext-ish X user interface robustness: The underlaying store handler (NODE) has been used since '89 and is quite stable. The system have betweem 20 to 500 users. description: LINCKS is an object-centred multi-user database system developed for complex information system applications where editing and browsing of information in the database is of paramount importance. The focus is on sharing of small information chunks which combine to make up complex information objects used by different users for different purposes. The information chunks are semi-structured in that they contain one part which is well-structured to facilitate addition of A.I. processing within the system, and one part which is unstructured and suitable for management by the user. Features: shared composite objects, database history, atlernative views, change collision notification (when more than one person makes changes to the same composite object) references: ftp://ftp.ida.liu.se/pub/lincks/articles/cscw.ps.gz announcements: lincks@ida.liu.se discussion: lincks-users-request@ida.liu.se bugs: lincks-bugs@ida.liu.se requires: Unix, X11R5 ports: Sun4/SunOS 4.1.[123], Sun4/SunOS 5.2, Sun3, Decstation, Alpha, RS/6000, Sequent Symmetry, Linux, HP-UX, SGI, SCO, SVR4.2, Sony restrictions: GNU General Public License author: Lin Padgham, Ralph Ronnquist; University of Linkoping, Sweden contact: lincks@ida.liu.se how to get: ftp pub/lincks/lincks-2.2.tar.gz from ftp.ida.liu.se usa: ftp pub/database/lincks/lincks-2.2.tar.gz from ftp.uu.net usa: ftp pub/net/infosys/lincks/lincks-2.2.tar.gz from gatekeeper.dec.com updated: 1994/06/05 name: OBST version: 3-4.3 interfaces: C++, tcl, schema compiler, graphical object browser access methods: extendable hashtable multiuser: yes, but writing locks entire tables transactions: yes distributed: not yet query language: C++, tcl, graphical object browser limits: 4 GB per container, 2^32 containers robustness: OBST is quite stable since the start of '93. Releases were made to enhance the coding quality rather than to add new features. There are somewhere between 50 and 500 users. description: The persistent object management system OBST was developed by Forschungszentrum Informatik (FZI) as a contribution to the STONE project (supported by grant no. ITS8902A7 from the BMFT, i.e. the German Ministry for Research). OBST was originally designed to serve as the common persistent object store for the tools of an software engineering environment. An essential feature of STONE is that the object oriented paradigm is pursued consequently as a key concept. OBST is the common persistent object store for all tools within the STONE environment. OBST provides a rich OO model including multiple inheritance, generics, overloading, and privacy. The schema definition language is syntactically similar to C++. It comes with a library of pre-defined classes like Set, and List. New methods can be incrementally loaded at runtime. announcements: send 'add obst-announce' to obst-listserv@fzi.de discussion: send 'add obst-forum' to obst-listserv@fzi.de bugs: send OBST version, configuration options, C++ version, machine, OS, and a description of your problem to . requires: A C++ compiler (G++ 2.3.3-2.6.3 or AT&T 2.1/3.01) ports: UNIX: SPARC/SunOS 4.1, Solaris 2, Linux, HP-UX, Ultrix, ... restrictions: STONE is over; OBST is now a commercial product. contact: obst@fzi.de how to get: ftp pub/OBST/OBST3-4.3 from ftp.fzi.de usa: ftp pub/database/obst/? from ftp.uu.net uk: ftp computing/databases/OBST/? from src.doc.ic.ac.uk updated: 1995/01/19 name: pfl version: 0.2 interfaces: Built-in persistent functional programming language access methods: no multiuser: no transactions: no distributed: no query language: functional programming limits: Index size is limited by the amount of main memory available. Selectors are a bit flaky when they contain more than about 10,000 tuples. Since the current implementation of the language is interpreted it is very slow. robustness: alpha release description: pfl is a persistent programming language and database environment. The language is functional. references: "An Overview of PFL", 3rd International Workshop on Database Programming Languages, 1991. "A functional programming approach to deductive databases", 17th International Conference on Very Large Databases, 1991 bugs: SunOS: author, Linux: Tim Holmes requires: GNU C++ ports: Linux, SunOS restrictions: GNU General Public License; educational use ? author: Carol Small contact: Tim Holmes how to get ftp pub/Linux/ALPHA/pfl-0.2.tgz from sunsite.unc.edu updated: 1994/09/21 name: The Texas Persistent Store version: 0.1 interfaces: C++ library access methods: ? multiuser: not yet transactions: not yet distributed: not yet query language: ? limits: ? robustness: beta software description: Texas is a simple, portable, high-performance persistent store for C++ using "pointer swizzling at page fault time" to translate persistent addresses to hardware-supported virtual addresses. Texas is built on top of a normal virtual memory, and relies on the underlying virtual memory system for caching. Texas is easy to use, and is implemented as a UNIX library. It is small and can be linked into applications. It requires no special operating system privileges, and persistence is orthogonal to type---objects may be allocated on either a conventional transient heap, or on the persistent heap, as desired. Texas supports simple checkpointing of heap data. references: ftp pub/garbage/*.ps from cs.utexas.edu announcements: send mail to oops@cs.utexas.edu discussion: ? bugs: ? requires: ? ports: SunOS, Ultrix, Sun CC, GNU C++ restrictions: ? author: ? contact: oops@cs.utexas.edu how to get: ftp pub/garbage/texas/? from cs.utexas.edu updated: ? name: Triton Object-Oriented Database System version: 1.1 interfaces: E, an Ada language binding. access methods: uses Exodus robustness: The support provided for Triton is limited. As resources permit, reported bugs will be fixed. Triton is reasonably robust and has been in daily use in Arcadia for several years primarily supporting APPL/A and Amadeus. description: Triton is an object-oriented database management system designed to support the Arcadia software engineering environment. It can be used as a general purpose DBMS, although it has specialized features to support the software process capabilities in Arcadia in the form of the APPL/A language. Triton provides for multi-language access and sharing of data, dynamic creation of classes (with methods) and objects, special support for relations, and special support for triggers. Triton uses a client-server architecture with data and methods held in the server. Triton is written in E, which is a persistent C++. What Triton adds to Exodus is another interface and a lot of higher-level functionality. This includes an Object Manager shell (catalog, trigger manager, and application objects); multi-language access and sharing; dynamic definition of schema and classes; schema catalog; and triggers before and/or after method invocations. references: http://www.ics.uci.edu/Arcadia requires: Exodus/E, DLD-3.2.3, Q 2.2, Arpc401.3a restrictions: GNU General Public License [I presume --ed] author: University of Colorado Arcadia Project. contact: Dennis Heimbigner how to get: ftp pub/cs/distribs/arcadia/? from ftp.cs.colorado.edu www: http://www.cs.colorado.edu/homes/arcadia/public_html/triton.html updated: ? name: William's Object Oriented Database (Wood) version: 0.6 interfaces: MCL 2.0 access methods: custom multiuser: no transactions: no distributed: no query language: none. Has BTrees for indexing. limits: Will slow down when the database size exceeds 256 megabytes. Otherwise, database size limited by disk size (up to Macintosh limit, which is, I believe, 4 gigabytes). Object size limited to 24 megabytes. If you think of a Wood database as a random access FASL file, you'll have the right idea. robustness: Until it has a real logging/recovery mechanism, I wouldn't advise using it for mission critical data. Caches pages in memory, so if you crash, you will lose. Has a function to flush the cache to disk, so you can do explicit checkpoints to make it more robust. description: Wood is a simple persistent store for MCL 2.0. This is still alpha software. It is incomplete: though you can save/restore all Lisp objects to/from a file, there is no transaction/recovery manager and no garbage collector for the persistent heap. I will not be able to provide much support, but you get source code. discussion: info-wood-request@cambridge.apple.com bugs: bug-wood@cambridge.apple.com ports: Macintosh CommonLisp 2.0 author: Bill St. Clair how to get: ftp pub/mcl2/contrib/wood* from cambridge.apple.com updated: 1993/03/07 name: YOODA (Yet another Object Oriented Database) version: 1.2 interfaces: C++ access methods: B+Tree multiuser: yes, client-server transactions: yes, but not yet nested. distributed: yes, you can distribute a database across multiple servers. Distributed access are completly transparent. User only specifies server when he creates an object. A Two phase commit mechanism is used to handle distributed commit. query language: C++ limits: 2 GB per volume, up to 256 volumes Memory mapping limits the total size of the objects accessed in a transactions (about 2 GB) robustness: beta software but pretty stable description YOODA is a small and simple Object Oriented Database. You can use it as a persistent C++ with transaction facilities in multi-clients/multi-server architecture. It uses virtual-memory mapping techniques. The key features of YOODA are: - A distributed database with multi-clients/multi-servers architecture. - CORBA like interface for communication. - Use of memory-mapping techniques - Transparent C++ interface through the use of a precompiler - Small size of the code (< 15000 lines). - Good performances - Good management of long objects status: actively developed announcements: comp.databases.object, send mail to ea@apic.fr discussion: send mail to ea@apic.fr bugs: send mail to ea@apic.fr requires: Unix, g++ 2.5.8 or later ports: SunOs 4.1.3, Alpha-OSF1 comming soon : HP-PA HP-Ux, Solaris 2.3, NextStep 3.0 restrictions: GNU Library General Public author: Eric Abecassis ea@apic.fr contact: author how to get: ftp pub/database/yooda from ftp.uu.net ftp pub/Unix/Database from ftp.fdn.fr updated: 1994/11/14 --------------------------------------------------------------------------- --------------------------- deductive databases --------------------------- --------------------------------------------------------------------------- name: Aditi Deductive Database System version: beta release interfaces: motif, command line, NU-Prolog access methods: Base relations contain variable sized records. Base relations can be indexed with B-trees or multi-level signature files (superimposed code words) allowing multi-attribute indexing and querying, or they can be stored as unindexed flat files. multiuser: yes transactions: next release distributed: ? query language: prolog, graphical (Motif) limits: ? robustness: ? description: Aditi is a multi-user deductive database system. It supports base relations defined by facts (relations in the sense of relational databases) and derived relations defined by rules that specify how to compute new information from old information. The old information can be from derived relations as well as base relations; the rules of derived relations may be recursive. Both base relations and the rules defining derived relations are stored on disk and are accessed as required during query evaluation. ports: SPARC/SunOS, MIPS/IRIX author: The development of the Aditi system started in 1988 by Professor Kotagiri Ramamohanarao, and many people have been involved in its development, in particular Jayen Vaghani, Tim Leask, Peter Stuckey, John Shepherd, Zoltan Somogyi, James Harland and David Kemp. The support of Kim Marriott, David Keegel, and Warwick Harvey is also acknowledged. contact: aditi@cs.mu.oz.au how to get: send email to aditi@cs.mu.oz.au updated: 1992/12/17 name: ConceptBase version: V3.3 interfaces: Prolog, C, C++ access methods: TELL and ASK multiuser: yes transactions: primitive (no concurrency) distributed: no query language: CBQL ("query classes") limits: system is rather slow for objects bases larger than 10000 objects robustness: used by 100+ institutes, thereby quite robust description: ConceptBase is a deductive object base manager, i.e., it combines object-oriented principles with logical deduction. It is useful for conceptual modeling and as a 'meta database' for heterogeneous information resources. Queries, deductive rules, and integrity constraints can be formulated at any abstraction level (instance, class, metaclass, ...) references: see http://www-i5.informatik.rwth-aachen.de/CBdoc/ bugs: CB@picasso.informatik.rwth-aachen.de ports: SunOS 4.1.3, Solaris 2.3 (both on SunSPARC) restrictions: ConceptBase is distributed by "contact", only. It is not public domain. The source agreeement prohibits commercial and military use. author: ConceptBase Team contact: staudt@informatik.rwth-aachen.de how to get: ftp /pub/CB from ftp.informatik.rwth-aachen.de updated: 1994/06/08 name: CORAL version: 1.2 interfaces: Exodus storage mangager, C++ access methods: Hash-based and B+ tree indices multiuser: When used with Exodus transactions: When used with Exodus distributed: ? query language: Prolog-like with SQL-style extensions; C++ interface limits: No type checking; only atomic values in persistent relations robustness: Research software; used for teaching and in research projects, but some bugs remain description: The CORAL deductive database/logic programming system was developed at the University of Wisconsin-Madison. The CORAL declarative language is based on Horn-clause rules with extensions like SQL's group-by and aggregation operators, and uses a Prolog-like syntax. Many evaluation techniques are supported, including bottom-up fixpoint evaluation and top-down backtracking. Disk-resident data is supported via an interface to the Exodus storage manager; however, CORAL can run without Exodus if disk-resident relations are not required. A good interface to C++ is provided. Relations defined using the declarative language can be manipulated from C++ code, and relations defined using C++ code can be used in declarative rules. C++ code defining relations can be incrementally loaded. references: http://www.cs.wisc.edu/coral/ requires: AT&T C++ 2.0 or later or g++ ports: Decstations, Sun 4, Sparc, HP Snakes author: The CORAL group consists of R. Ramakrishnan, P. Seshadri, D. Srivastava and S. Sudarshan. The following people made important contributions: T. Arora, P. Bothner, V. Karra and W.G. Roth. Several other people were also involved: J. Albert, T. Ball, L. Chan, M. Das, S. Goyal, R. Netzer and S. Sterner. contact: Raghu Ramakrishnan how to get: ftp from ftp.cs.wisc.edu updated: 1993/02/12 name: MOOD5 (Material's Object-Oriented Database) version: 1.0 interfaces: Virtually none. access methods: ? multiuser: no transactions: no distributed: no query language: Query-by-example object retrieval + some limits: The database is memory resident when in use and cannot exceed 16MB. robustness: Operation is fairly stable but by no means for mission-critical data. Mostly useful for experimentation. description: MOOD5 is an object-oriented database system written in Prolog. Unlike other general purpose OODBS, the system is meant to be used by non-programmer end-users with its unified user interface named the Object-Editor, or OE, in short. Therefore, the program may better be described as an OODB application. It is developed for the purpose of exprimenting the power of OODB in dealing with complex material data. As a result, it contains may novel features which are considered to be necessary to support material database practice such as the reasoning for data retrieval, the support of literal expressions for physical quantities, and so on. Interest from engineers/scientists who are to deal with a bulk of experimental data (not only from materials) and programmers in association with them are very much appreciated. announcements: comp.databases.object, sci.materials discussion: author bugs: author ports: IBM/NEC-PC/MS-DOS author: Noboru Ono how to get: ftp pub/mood from mood.mech.tohoku.ac.jp usa: ftp pub/database/mood from ftp.uu.net uk: ftp pub/computing/databases/mood from src.doc.ic.ac.uk updated: 1994/05/17 --------------------------------------------------------------------------- --------------------------- special purpose ------------------------------- --------------------------------------------------------------------------- name: GRAS (GRAph-oriented database System) version: 5.90/9 [[6.0 alpha]] interfaces: Navigational programming interfaces for C and Modula-2 access methods: tries fro database pages, static hashing within pages multiuser: Very restricted single writer/multiple reader access [[6.0: shared read/write access with locks on a per-session, transaction, or operation basis]] transactions: yes; based on backwards logs. Checkpoints allow roll-back (and roll-forward) to a previous state. distributed: no. [[6.0: Multiclient/multiserver architecture]] query language: PROGRES (PROgrammed Graph Rewriting Systems; a language released separately) limits: 2**16 nodes per database and 2**16 databases per multi-database [[6.0: 2**32 nodes]] robustness: Has been successfully used as the underlying database for a number of research prototypes and one commercial product. Guarantees recovery from (almost) all application/system crashes description: GRAS is a database system which has been designed according to the requirements resulting from software engineering applications. Software development environments are composed of tools which operate on complex, highly structured data. In order to model such data in a natural way, we have selected attributed graphs as GRAS' underlying data model. The current version has programming interfaces for Modula-2 and C and supports: - persistent attributed, directed node- and edge-labeled graphs (including long attributes and indexes) - temporary/volatile generic sets, binary relations, and lists, - graph modification triggers causing further modifications - primitives for version control comprising the capability for efficiently storing graphs as forward/backward deltas - primitives for declaring graph schemes and for incremental evaluation of derived attributes (constraints). In additon, there are tools for compressing and displaying graphs. The GRAS system may be considered to be the core of a graph oriented DBMS environment. The environment is based on a VHLL called PROGRESS. This environment supports: a syntax-directed editor for graph schemes, rewrite rules and sequences of rules; an incremental consistency checker; an incremental compiler&interpreter for PROGRESS; an enhanced graph browser references: Kiesel, Schuerr, Westfechtel: GRAS, A Graph-Oriented Database System for (Software) Engineering Applications. Proc. CASE 93, Lee, Reid, Jarzabek (eds.): Proc. CASE '93, 6th Int. Conf. on Computer-Aided Software Engineering, IEEE Computer Society Press (1993), pp 272-286. Available by ftp as TR AIB 92-44. Schuerr: PROGRES: A VHL-Language Based on Graph Grammars, in Proc. 4th Int. Workshop on Graph-Grammars and Their Application to Computer Science, LNCS 532, Springer- Verlag 1991, pp 641-659. Available by ftp asTR AIB 90-16. announcements: a list is forming; send mail to the contact (below) bugs: use the included "send-pr" program to send bug reports requires: Modula-2, C ports: Sun-4, porting requires Modula-2 restrictions: GNU General Public License author: Lehrstuhl fuer Informatik III, RWTH Aachen, Ahornstr. 55 D-52074 Aachen, Germany. contact: (v5.x & PROGRES) Dr. Andy Sch"urr (v6.x) Norbert Kiesel how to get: (v5.x) ftp pub/unix/GRAS from ftp.informatik.rwth-aachen.de (PROGRES sun4) ftp pub/unix/PROGRES from ftp.informatik.rwth-aachen.de (PROGRES source) send mail to contact (references) ftp pub/reports/* from ftp.informatik.rwth-aachen.de (v6.x) contact Norbert Kiesel updated: 1993/11/01 --------------------------------------------------------------------------- --------------------------- flat files ------------------------------------ --------------------------------------------------------------------------- name: AddressManager version: 0.1 interfaces: Tcl/Tk multiuser: no transactions: no distributed: no query language: none limits: ? robustness: ? description: A graphical rolodex requires: wish author: Chunping Ding how to get: ftp pub/addressManager.tar.gz from banff.cssip.edu.au usa: ftp pub/tcl/code/addressManager.* from harbor.ecn.purdue.edu updated: 1994/05/12 name: EDB, the Emacs database version: 1.19 interfaces: Emacs, Emacs Lisp multiuser: no transactions: no distributed: no query language: Emacs Lisp limits: same as for Emacs -- typically 8 or 32 MB robustness: fairly high -- currently being used for mission-critical data description: EDB provides simple database access in a "user-friendly" Emacs environment for flat files. Extensions for linking records and relational-like operations exist, and further extensions are easy to make. EDB is documented by a 110-page manual, complete with indices discussion: edb-list-request@theory.lcs.mit.edu bugs: mernst@theory.lcs.mit.edu or edb-list@theory.lcs.mit.edu requires: GNU Emacs 18, GNU Emacs 19, or Lucid Emacs ports: any computer that runs Emacs -- that is, almost any computer restrictions: GNU Public License author: Michael Ernst how to get: ftp pub/emacs/edb/edb-*.tar.gz from theory.lcs.mit.edu updated: 1994/11/15 name: grok (Graphical Resource Organizer Kit) version: 1.1 interfaces: query language, GUI, GUI builder access methods: ? multiuser: no transactions: no distributed: no query language: custom limits: ? robustness: one user recommends against use as a payroll database description: Grok is a simple database manager and UI builder that can keep phone lists; store phone call logs; store todo lists; and manage any other database after simple GUI-driven customization. More precisely, grok is a program for displaying and editing strings arranged in a grid of rows and columns. Each row is presented as a "card" consisting of multiple columns, or "fields", that allow data entry. The presentation of the data is programmable; a user interface builder that allows the user to arrange fields on a card graphically is part of grok. Grok also supports a simple language that allows sophisticated queries and data retrieval. ports: IRIX, HP-UX, AIX. restrictions: ? author: Thomas Driemeyer how to get: ftp programs/X/grok* from swedishchef.lerc.nasa.gov ftp pub/unix/graphics/grok from ftp.fu-berlin.de updated: 1994/11/17 name: Jinx version: 2.1 interfaces: perl, shell multiuser: no transactions: no distributed: no query language: none limits: no limits robustness: No bugs have ever been reported description: Very easy to use, curses based flat file handler. In Perl, so no limits. Allows Join, Project, Sort etc. Representation in 2 readable unix files. A documented Perl library makes it easy to add applications. references: Online help and a 17 page tutorial. requires: Perl, cterm (distributed with jinx) ports: any unix system with ordinary perl and curses restrictions: Copyleft author: Henk Penning, Utrecht University contact: Henk Penning how to get: ftp pub/PERL/jinx.shar.Z and pub/PERL/cterm.shar.Z from ftp.cs.ruu.nl updated: 1991/11/01 name: rdb version: 2.5k interfaces: perl, shell, UNIX tools access methods: binary search, linear scan multiuser: restricted single writer/multiple reader access transactions: no distributed: no query language: none limits: no limits robustness: Is being used on many research projects; no known bugs. description: RDB is a fast, portable, Relational DataBase Management System that works with relational data in ascii files. RDB is a set of Perl modules working as filters, like "row", "column" & "join" ; a very nifty table formatting script is in "ptbl", which can do long field folding into multiple lines per row. Also includes a general report generation capability. references: Included documentation; Each module has online help. announcements: comp.lang.perl; also author email list of current users. discussion: author ports: any unix system (or other OS with redirection of I/O). author: Walt Hobbs how to get: ftp pub/RDB-hobbs/RDB-2.5j.tar.Z from rand.org updated: 1994/06/20 --------------------------------------------------------------------------- ----------------- dbm and other and raw access methods ------------------- --------------------------------------------------------------------------- name: The Berkeley DB code version: 1.85 interfaces: ndbm, hsearch access methods: hash, b+tree, recno multiuser: no transactions: no distributed: no query language: none limits: can handle large items robustness: The db routines are used in some production code so they are likely to work reasonably well. description: The Berkeley DB Code is a unification of several previous interfaces. It also forms the basis of a unified interface to new access methods (b+tree, recno). references: "A New Hashing Package for UNIX", Margo Seltzer, Ozan Yigit, Proceedings of the Winter USENIX Conference, Dallas, TX, 1991. Also available by ftp'ing pub/oz/hash.ps.Z from nexus.yorku.ca. "Document Processing in a Relational Database System, Michael Stonebraker," Heidi Stettner, Joseph Kalash, Antonin Guttman, Nadene Lynn, Memorandum No. UCB/ERL M82/32, May 1982. "LIBTP: Portable, Modular Transactions for UNIX," Margo Seltzer, Michael Olson, Proceedings 1992 Winter Usenix Conference, San Francisco, CA, January 1992. reported bugs: does not align data in memory [fixed? --ed] ports: SunOS 4.1.2, Ultrix 4.2A, BSD 4.4, and most other Unix author: Margo Seltzer, Keith Bostic, Ozan Yigit contact: Keith Bostic how to get: ftp ucb/4bsd/db.tar.gz from ftp.cs.berkeley.edu updated: 1994/09/01 name: Btree Library version: first public release interfaces: raw C library access methods: b-tree multiuser: no transactions: no distributed: no query language: none limits: values are limited to 4 bytes (long enough for a pointer!) robustness: ? description: Ths is a library that maintains a simple balanced btree index. Nothing more is provided than routines to insert, set, find (specific, next, and previous), and delete keys. Each key, however, has a spare long value that can be used to contain an offset to a data file. A library to handle fixed-length records based on these pointers should be trivial. (Can you say 'dBASEIII'?) Another failing of this library is its total inability to cope with having several programs modifying indices at the same time. (it *CAN*, but I won't vouch for the result) The good solutions to that particular problem are OS dependent, unfortunately, and I am not a database guru anyhow. ports: Unix author: Marcus J. Ranum how to get: get btree and bt-rio from comp.sources.misc volume 3 updated: 1988/06/02 name: B+tree Library version: first public release interfaces: raw C library, dbm-like library access methods: b+tree multiuser: no transactions: no distributed: no query language: none limits: ? robustness: ? description: This is the source code for a variable-length key variable page size b+tree library. Also included is source for a variety of test programs, a semi-useable record manager, and a dbm-lookalike library built on top of the record manager and b+tree. (dbm(3) will blow it away performance-wise, of course). ports: Pyramid, Sun, BSD4.3, Ultrix. Does not work on Xenix author: Marcus J. Ranum how to get: get b+tree_mgr from comp.sources.misc volume 10 updated: 1988/06/02 name: cbase version: 102 interfaces: C access methods: ISAM multiuser: no transactions: ? distributed: no query language: none limits: ? robustness: ? description: A database library (ISAM like). ports: MS-DOS restrictions: ? contact: ? how to get: ftp pub3c/SimTel/msdos/c/cbase102.zip from ftp.ibp.fr updated: ? name: dbc3 version: 1.0 interfaces: raw C library access methods: ? multiuser: no transactions: ? distributed: no query language: none limits: ? robustness: ? description: Dbclib provides a basic C interface to the database files used by dBase III. It provides funtions to both read and write them. The author is German and so all the comments are in German. It's very small (95k). [I'm not sure I have the name correct --ed] ports: Unix, MS-DOS author: D.Schanz how to get: uucp (host gold, login nuucp, no password, phone 08106-34593) /home/public/unxhigh/unix1/dbclib.tgz; or ftp pub/pc/dos/programming/c/dbclib.tar.gz from ftp.uni-kl.de updated: 1988/09/13 name: dbz version: "20 Feb 1993 Performance Release of C News" interfaces: dbm-like, command-line access access methods: hash multiuser: no transactions: no distributed: no query language: none limits: lines are limited to 1024 bytes unless the -l option is used robustness: very robust within its domain description: A dbm-like library maintained for use with C-news. ports: everything that runs C-news (lots) author: Jon Zeeff , David Butler, Mark Moraes, Henry Spencer. Hashing function by Peter Honeyman. contact: Henry Spencer how to get: included in the C-news distribution as ./dbz updated: 1992/02/11 name: gdbm version: 1.7.3 interfaces: dbm, ndbm, gdbm access methods: hash multiuser: no, but does lock the entire file transactions: no distributed: no query language: none limits: can handle large items robustness: [should be good --ed] description: An ndbm work-alike from the Free Software Foundation bugs: gnu.utils.bug author: Philip A. Nelson how to get: ftp gdbm-*.tar.gz from any gnu archive updated: 1994/05/18 name: HDS (Hierarchical Data System) version: ? interfaces: Fortran, C? access methods: ? multiuser: ? transactions: ? distributed: no query language: ? limits: ? robustness: ? description: [This is probably just a library, but it may be a full database --ed] A library for storing large multi-dimensional arrays where efficiency of access is a requirement. It is presently used in astronomy, for storing (in particular) images, spectra and time series. references: http://star-www.rl.ac.uk/ ports: Alpha OSF/1, Sparc SunOS, Sparc Solaris restrictions: ? contact: ? mdl@star.rl.ac.uk ? how to get: ftp pub/doc/star-docs/sun92.tex from starlink-ftp.rl.ac.uk updated: ? name: IDBM (ISAM Database Manager) version: 0.2.0 interfaces: C library, curses query facility access methods: ISAM multiuser: no transactions: no ? distributed: no query language: none limits: ? robustness: beta release description: IDBM is a fairly complete ISAM database system. It includes a database library, a schema compiler, a database consistaency checker, import and export routines, and curses programs to modify the database schema and the data in the database. references: ? announcements: ? discussion: ? bugs: ? requires: ? ports: Xenix, SysV, HP-UX, AIX, Amiga, SunOS, BSD, and Ultrix restrictions: May not be used for commercial purposes. author: John F Haugh II contact: ? how to get: ftp pub/idbm/idbm-0.2.x/* from ftp.nevada.edu updated: 1992/03/31 name: sdbm version: ? interfaces: ndbm access methods: hash multiuser: no transactions: no distributed: no query language: none limits: ? robustness: [I know of no problems --ed] description: ndbm work-alike hashed database library based on Per-Aake Larson's Dynamic Hashing algorithms. author: Ozan S. Yigit how to get: included in the X11R5 distribution as contrib/util/sdbm updated: 1990/03/01 name: tdbm version: 1.2 interfaces: dbm-like access methods: hashing multiuser: In theory, but the required threads package is not currently distributed. transactions: yes distributed: yes query language: none limits: Some minor ones. robustness: Probably pretty reliable, but no hard data available. description: Tdbm is a transaction processing database with a dbm-like interface. It provides nested atomic transactions, volatile and persistent databases, and support for very large objects and distributed operation. references: A paper appearing in the Summer '92 USENIX proceedings describes the design and implementation of tdbm and examines its performance. discussion: Contact the author. bugs: Contact the author. author: Barry Brachman requires: Nothing special. ports: Sparc, MIPS, AIX. Thought to be quite portable. restrictions: Copyrighted with liberal use policy. how to get: ftp pub/local/src/tdbm-1.2.tar.gz from ftp.cs.ubc.ca updated: 1994/07/06 name: Wb version: 1a2 interfaces: scheme library access method: b-tree multiuser: no transactions: no distributed: no query language: none limits: keys and data must be less that 256 bytes. Total database must be < blocksize*2^32. robustness: unknown. New release by a good programmer. description: WB is a disk based, sorted associative array C library. These associative arrays consist of variable length (less that 256 bytes) keys and values. WB comes with an interface to the Scheme implementation SCM. author: Aubrey Jaffer requires: SCM and SLIB (also available from altdorf.ai.mit.edu) ports: ? how to get: ftp archive/scm/wb1a2.tar.z from altdorf.ai.mit.edu updated: 1993/11/05 name: YACL (Yet Another Class Library) version: ? interfaces: C++ library access methods: variable-length record management, b-trees. multiuser: no transactions: no distributed: no query language: none limits: ? robustness: ? description: YACL is a general-purpose C++ class library. It happens to include some disk access methods. ports: MS Windows, Linux restrictions: Commercial use prohibited. author: M. A. Sridhar how to get: ftp pub/sridhar/yacl.zip from ftp.cs.scarolina.edu updated: 1994/05/25 --------------------------------------------------------------------------- --------------------------- full text ------------------------------------- --------------------------------------------------------------------------- name: FFW version: 1.01 interfaces: command line -- intended for CGI scripts access methods: inverted index ? query language: formal expression grammar with AND, OR, NOT and (). index size: 30-50% of data size limits: ? robustness: ? description: Freetext search For Web (FFW) s a package made to provide easy-to-use freetext searching facilities over HTML documents (and as a special case plain text documents). The output is intended as input to scripts providing the user interface, typically CGI scripts. FFW is basically intended to replace similar solutions based on the Wais search engine, and solves some of the problems we experienced when using the Wais engine. FFW supports HTML. It parses input files, ignoring HTML directives and translating HTML special characters into ISO8859-1 equivalents. FFW can build indexes incrementally and can search multiple indexes at the same time. Program messages are separated in one file for easy nationalisation. Norwegian and English versions are provided. references: http://www.nta.no/produkter/ffw/ffw.html requires: g++ 2.6.2 exactly, g++ library ports: SunOS 4.1.3 author: Ken Ronny Schouten, Haiyan Yang, Berd Hefjeld: MultiTorg project at TeleNor Research, Norway. contact: ffw@nta.no how to get: ftp pub/ffw/ from ftp.nta.no updated: 1995/01/09 name: glimpse version: 1.0 interfaces: command line access methods: ? query language: logical conjunctions in command line searches index size: 2-4% limits: does not work well with source text larger than 500MB robustness: ? description: Glimpse is a text pre-scanning and query tool. It builds a database of which files a word is used in. When you want to search for a word, it knows ahead of time where it needs to look. This allows it to give very quick results without storing a large inverted index. references: U. Manber and S. Wu, "GLIMPSE: A Tool to Search Through Entire File Systems," Usenix Winter 1994 Technical Conference, San Francisco (January 1994), pp. 23-32. Also, Technical Report #TR 93-34, Dept. of Computer Science, University of Arizona, October 1993 (a postscript file is available by anonymous ftp at cs.arizona.edu:reports/1993/TR93-34.ps). S. Wu and U. Manber, "Fast Text Searching Allowing Errors," Communications of the ACM 35 (October 1992), pp. 83-91. discussion: glimpse-request@cs.arizona.edu ports: portable, binaries provided for sun, mips, linux and alpha author: Udi Manber, Sun Wu, and Burra Gopal, Department of Computer Science, University of Arizona. contact: glimpse@cs.arizona.edu how to get: ftp glimpse/* from cs.arizona.edu updated: 1994/04/27 name: Liam Quin's text retrieval package (lq-text) version: 1.13 interfaces: command line, curses access methods: hash (dbm) plus clustered linked list multiuser: read only distributed: no, can be used over nfs if the systems are similar query language: very limited command line limits: 30-bit max document size, 31-bit distinct words in vocabulary, up to 2^24 documents (possibly more but I don't have enough disk to test anything like that!) index size: >30%, <100% of input text robustness: The README says that there are bugs. description: lq-text is a text retrieval package. That means you can tell it about lots of files, and later you can ask it questions about them. The questions have to be: "which files contain this word?" or "which files contain this phrase?", but this information turns out to be rather useful. Lqtext has been designed to be reasonably fast. It uses an inverted index, which is simply a kind of database. This tends to be smaller than the size of the data, but more than half as large. You still need to keep the original data. Lqtext uses dbm (berkeley db or sdbm) to store its indexes. discussion: lq-text-beta-request@sq.com bugs: lq-text-beta@sq.com ports: most version of unix (except SCO) restrictions: permission required for commercial use. author: Liam R. E. Quin how to get: ftp pub/lq-text*.tar.Z from relay.cs.toronto.edu updated: 1993/12/10 name: mg version: 1.0 interfaces: command line interpreter, X (tcl) access methods: ? multiuser: no transactions: no distributed: no query language: boolean and ranked queries using cosine similarity measure index size: 5-15% of text being indexed, depending on document size and richness of vocabulary. Text is also stored compressed, requires around 25-30% of original size. Complete retrieval system requires 30-45% of original text size. limits: Will probably fail when used with > 4Gb robustness: It is a research prototype, and as such there are no guarantees. Don't rely on it as a primary archive tool; but it is very useful as an adjunct to other storage mechanisms for e.g. maintaining a personal mail retrieval system. And, of course, for research purposes. description: mg compresses and indexes documents and images (indexed by user-supplied textual description). All components are stored compressed: text by a word-based method that reduces the space requiremnent to around 25% of input; images by one of three different methods (FELICS, Textual Image Compression, two-level image compression); and index using index compression methods. The package also includes a mechanism for fast and economical creation of the index in thge first place. It requires about 8 hours (Sun SPARC 10 Model 512) to compress and index 2 Gb of text (the TREC collection); final retrieval system requires about 700 Mb to operate. Multi-term Boolean and ranked queries are answered within seconds. references: "Managing gigabytes: compressing and indexing documents and images", Witten, Moffat, and Bell, Van Nostrand Reinhold, 1994, ISBN 0-442-01863-0. "Compression and fast indexing for multi-gigabyte text databases", Moffat and Zobel, Australian Computer Journal, 26(1):1-9, February 1994. status: actively-develped research prototype. Support of public use is not a priority. ports: SunOS, Solaris, SGI, Ultrix, NeXT. restrictions: GNU General Public License author: Tim Bell , Stuart Inglis , Alistair Moffat , Neil Sharman , Tim Shimmin , Ian Witten , Justin Zobel , and others. contact: Alistair Moffat how to get: ftp pub/mg from munnari.oz.au updated: 1994/03 name: qt (Query Text) version: 0.1 interfaces: unix command line access methods: ? multiuser: no distributed: no query language: unix command line index size: ? limits: ? robustness: ? description: Qt creates, maintains, and queries a full text database. The database file system is organized as an inverted index. The program is written as a single script, in Bourne Shell, and permits simple natural language queries. [qt appears to be easier to use than lq-text and wais --ed] bugs: author ports: Unix, SysV.4, AIX, OSF/1, etc. author: John Conover how to get: comp.sources.unix volume 27 updated: 1993/10/18 name: SMART version: 11.0 interfaces: terminal, X (slightly oder version), and several under development including Z39.50 access methods: inverted file search or sequential search multiuser: yes, but last writer wins when there are update conflicts distributed: In-house version, to be made public in fall query language: Natural language index size: approx 40% of original text. limits: Can only handle roughly 4 Gbytes of text in non-distributed version. robustness: Research tool; parts have been well-tested but others not. description: SMART is an implementation of the vector-space model of information retrieval proposed by Salton back in the 60's. The primary purpose of SMART is to provide a framework in which to conduct information retrieval research. Standard versions of indexing, retrieval, and evaluation are provided. The system is designed to be used for small to medium scale collections, and offers reasonable speed and support for these actual applications. SMART analyses the collection of information and builds indexes. It can then be used to build natural-language based information retrieval software. It uses feedback from the user to tighten its search. references: Z39.50 URL: restrictions: Research use only. discussion: smart-people-request@cs.cornell.edu ports: Unix (works under Linux, does not work under Ultrix, ?) contact: how to get: ftp pub/smart/* from ftp.cs.cornell.edu updated: 1992/07/21 name: WAIS (Wide Area Information Server) version: 8 b5.1 interfaces: the wais protocol (Z39.50) access methods: inverted string index multiuser: read only distributed: client/server query language: natural language, boolean, Relevance Feedback index size: roughtly = data size limits: "none" robustness: fairly high description: There are three main components: WAISINDEX, WAISSERVER, and WAISSEARCH. WAISINDEX creates an inverted file index. WAISINDEX includes filters for a number of common file formats. WAISSERVER listens for Z39.50 packets and tries to answer them. WAISSEARCH is the user agent that talks to WAISSERVERs. There are several front ends: shell, X, and emacs. announcements: wais-interest-request@think.com discussion: wais-discussion-request@think.com ports: vax, sun-3, sun-4, NeXT, sysV restriction: commercial version exists, contact info@wais.com author: Harry Morris , Brewster Kahle , Jonny Goldman how to get: ftp pub/freeware/unix-src/* from wais.com updated: 1992/11/16 --------------------------------------------------------------------------- --------------------------- interfaces ------------------------------------ --------------------------------------------------------------------------- name: AdaSAGE version: ? interfaces: SQL, embedded SQL. transactions: yes distributed: ? query language: SQL robustness: ? description: AdaSAGE is not a DBMS. AdaSAGE is an application development tool that provides facilities for creating an application specific relational data base. There are two aspects of SQL dialog to consider. First is listening to SQL and responding by executing the requested command. Second is issuing SQL to get a foreign system to execute some process on your behalf. In the first case AdaSAGE provides both an embedded SQL technology and an interactive SQL system adapted to comply with ANSI-SQL DML Level 1. In the second case AdaSAGE does not provide any capabilities for creating SQL commands, but since AdaSAGE is a set of Ada packages there is no reason that a package could not be developed to do so. The capability to record all transactions and roll forward from previous dates gives an audit trail and recover capability. These features are often provided within data base management systems, and are provided with AdaSAGE as a logging option, but seldom if ever are they used in final applications because of the excessive time and data storage requirements. references: ? announcements: ? discussion: ? bugs: ? requires: Ada ports: MS-DOS, UNIX restrictions: Use restricted to US DoD, DoE and educational institutions. contact: ? how to get: ftp pub/sage/* from navair1.inel.gov updated: ? name: CB++ version: 0.1 interface from: C/C++ interface to: SunOS/Oracle (DOS+Windows/Oracle,Gupta, OS/2 Sybase) description: CB++ provides a plain C/C++ interface (not embedded) for SQL database server access. It was written in 1989 as a basis for storing C++ objects in a relational database. It is very simple to use and makes applications portable among different SQL databases. The library itself is relatively easy to port as the database vendor specific code is separated into a single C++ class which makes up only a limited part of the library. The author supports the current SunOS/Oracle version and server ports to other UNIX databases (DOS-, Windows-, OS/2-stuff is provided as it is and no longer supported) requires: C++ ports: Oracle 6 for SunOS 4.1.3, Gupta SQL Server for DOS/MS-Windows, OS/2 SQL Server author: Bernhard Strassl how to get: ftp R5contrib/CB++.0.1.tar.Z from ftp.x.org updated: 1993/10/05 name: ChezSybase (A blatent trademark ripoff) version: 1.0 interface from: Chez Scheme interface to: Sybase limits: limited text datatype support -- text datatype only up to 32K -- the Sybase returned SQL column limit, image and binary data not supported, datetime Sybase data must be manipulated as strings in Scheme, a few db-lib calls not implimented description: A foreign function interface to Chez Scheme to allow calls to the Sybase db-lib, the API to the Sybase database, and a high level Scheme-like interface so you can forget about db-lib. bugs: Contact the author. requires: Chez Scheme, Sybase db-lib & server, network support for Sybase ports: VMS, should work in Unix author: Karl O. Pinc how to get: ftp ftp.cs.cmu.edu:/user/ai/lang/scheme/code/io/chez_syb ftp ftp.cs.indiania.edu:/pub/scheme-repository/ updated: 1991/08/07 name: ciORA version: alpha interface from: C interface to: Oracle query language: ? robustness: ? description: ciORA is a set of C interface routines to Oracle that are modeled after the standard I/O portion of the C library. ciORA presents a familiar interface to an experienced C programmer by avoiding the awkward embedding of SQL statements using precompilers and the tedium of using low-level OCI calls. ciORA eliminates the need for precompilers by supplying an interface library providing equivalent functions. It also provides a higher level of abstraction to the functions in the Oracle Call Interface (OCI). ciORA manages (and hides) the tedious details necessary when writing programs using OCI by replacing the cumbersome Oracle constructs such as logon data areas, cursor data areas, and external datatypes, the Oracle array interface, bind variables, select-list-items, and the like with constructs familiar to a C programmer using the standard I/O portion of the C library. ciORA also provides a consistent interface to Oracle errors similar to the convention used in C's errno. requires: Oracle ports: IRIX 5.2, Oracle 7.0.15.4.0 restrictions: GNU General Public License author: Zane Dodson how to get: email author updated: 1994/09/10 name: cisamperl version: 0.9 interface from: perl interface to: Informix C-ISAM 3.1 library limits: ? robustness: ? description: cisamperl/rocisperl is a package, which implements an interface to the INFORMIX C-ISAM library for perl. It is coded as an usub (see perl documentation) and needs to be compiled with perl and the C-ISAM library to form 2 separate executables called cisamperl and rocisperl respectively. cisamperl is a fully functioning (unless I forgot something) perl executable with calls for C-ISAM file access added. rocisperl is the same, with all calls that create/modify/delete C-ISAM files or records disabled. requires: C-ISAM 3.1, perl4 ports: ? author: Mathias Koerber how to get: ftp pub/perl/db/perl4/cisamperl/cisamperl-* from ftp.demon.co.uk updated: 1994/10/29 name: ctreeperl version: ? interface from: perl interface to: FairCom Ctree description: A perl interface for FairCom Ctree file indexing. requires: Ctree author: John Conover how to get: ftp pub/perl/db/ctreeperl from ftp.demon.co.uk updated: 1994/04/07 name: dbf (xbase manipulation package) version: ? interface from: command line interface to: xbase files access methods: ? multiuser: no transactions: no distributed: no query language: none limits: ? robustness: ? description: DBF is a set of tools and library routines to manipulate xbase files. The tools allow xbase files to be created and manipulated from the command line. author: Brad Eacker how to get: comp.sources.misc volume 43 updated: 1994/06/27 name: dbf read routines in perl version: ? interface from: perl interface to: xbase files description: very simple (15 line) routines to read dbf files author: David Rensin how to get: ftp pub/source/read_dbf_in_perl from ftp.idiom.com updated: 1994/11/13 name: DSQL version: 3.0 interface from: Unix, Macintosh, MS-DOS, MS-Windows, and Macintosh Hypercard interface to: Unix/Informix, VMS/Oracle description: DSQL is a simple client/server protocol to support remote access of SQL databases. DSQL was designed in response to a perceived need at Genentech to provide graphical front-ends on Macintosh computers to Informix relational databases running on Unix servers. DSQL version 3 is distributed with 2 server implementations and four client library implementations. The API for the client libraries has been standardized, and the client code is divided into portable and architecture-specific portions. requires: ? ports: Mac, PC, Unix author: The Genentech Scientific Computing Technology Development group. Original authors: David Mischel, Terry Oberzeir, Scooter Morris , Kathryn Woods. Current team: Jim Fitzgerald, David Mischel, Scooter Morris, Terry Oberzier, and Dan Lamb (VMS/Oracle). contact: ? how to get: ftp pub/dsql.3.tar.Z from cgl.ucsf.edu updated: 1993/06/25 name: Ingperl version: 2.0 interface from: perl interface to: Ingres descritpion: Ingperl is a set of user subroutines to enable Perl programs to access Ingres databases. Ingperl used to be called Sqlperl. requires: Perl 3.027 or higher, ? discussion: perldb-interest-REQUEST@vix.com author: Ted Lemon how to get: ftp pub/perl/db/sqlperl/? from ftp.demon.co.uk updated: 1994/04/11 name: Isqlperl version: 1.1 interface from: perl interface to: Informix limits: Maximum concurrently open cursors configured at build time. descritpion: Isqlperl is a set of user subroutines to enable Perl programs to access Informix databases. requires: Perl 4.035 or higher, Informix ESQL/C (Online, SE, or Turbo) discussion: perldb-interest-REQUEST@vix.com restrictions: GNU Public License author: Bill Hails how to get: ftp pub/perl/db/isqlperl/isqlperl-1.1.shar.Z from ftp.demon.co.uk updated: 1993/10/02 name: Isqltcl ? version: ? interface from: tcl interface to: Informix description: Isqltcl is an extension to Tool Command Language (Tcl) that provides access to an Informix database server. Isqltcl adds additional Tcl commands that login to an Informix Server, pass SQL code, read results, etc. requires: ? discussion: comp.lang.tcl author: Srinivas Kumar how to get: ftp tcl/extensions/isqltcl.tar.Z from harbor.ecn.purdue.edu updated: 1993/09/15 name: Interperl version: ? interface from: perl interface to: Interbase descritpion: Interperl is a set of user subroutines to enable Perl programs to access Interbase databases. requires: Perl 3.027 or higher, ? discussion: perldb-interest-REQUEST@vix.com author: Buzz Moschetti how to get: ftp pub/perl/db/interperl/? from ftp.demon.co.uk updated: ? name: Onyx version: 2.34 interface from: Onyx 4gl, (emacs and smalltalk planned) interface to: Ingres89, Informix, GAWK, Shql, Yard, Minerva SQL, SqlPostgres (OBST planned) The informix port is slow and no longer being extended because the author feels their support is inadiquate. interfaces: Onyx uses a OO-Parser to access different engines The transaction manager can be accessed by any aplication which is able to use pipes or TCP/sockets. multiuser: Depends on the used engine. transactions: Yes, but no rollback, all transactions are atomic as a block, replication of transactions is planned for one of the next releases. distributed: Yes its possible to connect to any mentioned database anywhere in the net. Replication is planned. query language: SQL + Onyx 4gl (based on Model-View-Controller idea) limits: Current version uses memory to store selected data. robustness: Onyx is experimental, but useable for clients. The author is supporting himself by writing applications written in Onyx 4GL. description: Onyx is a 4gl based on the idea of model view controller. Onyx 4gl connects to a transaction manager based on a OO-Parser generator via a socket. While the design goal of the protocol was to keep it as simple as posible, its a good starting point of writing vendor independent database applications. status: experimental; actively developed and supported. announcements: comp.os.linux.announce bugs: Michael Koehne requires: BSD like system, GNU C++, a database engine (minimum GNU-AWK) ports: Tested on Linux and SunOs. restrictions: GNU Public Licence author: Michael Kraehe how to get: ftp incoming/onyx/? from ftp.germany.eu.net (every versions) ftp pub/comp/i386/Linux/Local.EUnet/Applications/Database from ftp.germany.eu.net (stable versions) updated: 1994/12/01 name: Oraperl version: ? interface from: perl interface to: Oracle descritpion: Oraperl is a set of user subroutines to enable Perl programs to access Oracle databases. requires: Perl 3.027 or higher, Oracle Pro*C discussion: perldb-interest-REQUEST@vix.com author: Kevin Stock how to get: ftp pub/perl/db/oraperl/? from ftp.demon.co.uk updated: ? name: Oratcl version: 2.2 interface from: TCL interface to: Oracle description: Oratcl is an extension to Tool Command Language (Tcl) that provides access to a Oracle Database server. Oratcl adds additional Tcl commands that login to an Oracle Server, pass SQL code, read results, etc. Oratcl was inspired by similar tools written for Perl (sybperl, oraperl) but was written from scratch instead of borrowing on the work of either Perl extension. requires: Tcl 6.7, Tk 3.2, Oracle OCI libraries 1.5, Oracle SQL Server Version 6 or Version 7 discussion: comp.lang.tcl author: Tom Poindexter how to get: ftp tcl/extensions/oratcl-2.2.tar.gz from ftp.aud.alcatel.com updated: 1994/11/04 name: pgperl version: ? interface from: perl interface to: Postgres descritpion: pgperl is a set of user subroutines to enable Perl programs to access Postgres databases. requires: Perl 3.027 or higher, ? discussion: perldb-interest-REQUEST@vix.com author: Igor Metz how to get: ftp pub/perl/db/pgperl/? from ftp.demon.co.uk updated: ? name: SIOD (Scheme In One Defun/Day) version: 3.0 interface from: C, C++, Scheme interface to: Oracle, Digital RDB, flat ascii, flat binary. access methods: flat files contain symbolic expression such as hash tables. multiuser: yes with commercial DB, no with flat files. transactions: yes with commercial DB, no with flat files. distributed: yes with commercial DB, no with flat files. query language: SQL, any SCHEME program. limits: None. robustness: ? description: This is a scheme interpreter with built-in procedures using the Oracle Call Interface (OCI) and DIGITAL RDB SQL Services. You can use it merely as a flexible database loader/unloader with fast binary flat-file data save/restore. Or you can use it to apply the classic "Symbolic Manipulation" or "Artificial Intelligence" techniques on your data sets. The main-program can be oriented towards batch, character-cell terminal, or Window/GUI. references: "Structure and Interpretation of Computer Programs" MIT Press. announcements: comp.lang.scheme, comp.databases.rdb, comp.databases.oracle bugs: Contact the author. requires: C compiler, your favorite commercial DB. ports: VMS, WINDOWS NT, UNIX, OS/2, MACINTOSH. author: George Carrette how to get: ftp pub/gjc/siod* from ftp.std.com. updated: 1994/05/01 name: Sybperl version: 1.011 patch 12 interface from: perl4 interface to: Sybase descritpion: Sybperl is a set of user subroutines to enable Perl programs to access Sybase databases. requires: Perl 3.027 or higher, ? discussion: perldb-interest-REQUEST@vix.com author: Michael Peppler how to get: ftp pub/perl/db/mod/Sybperl/ from ftp.demon.co.uk updated: 1994/12/22 name: Sybperl version: 2a7 (a is for alpha) interface from: Perl5 interface to: Sybase descritpion: Sybperl is a set of user subroutines to enable Perl programs to access Sybase databases. Sybase::DBlib implements a fairly large subset of Sybase's DBlibrary API in the Perl5 fashion (ie using some of the new OO features of Perl5) requires: perl5 discussion: perldb-interest-REQUEST@vix.com author: Michael Peppler how to get: ftp pub/perl/db/mod/Sybperl/ from ftp.demon.co.uk updated: 1994/12/22 name: Sybtcl version: 2.2 interface from: TCL interface to: Sybase description: Sybtcl is an extension to Tool Command Language (Tcl) that provides access to a Sybase Database server. Sybtcl adds additional Tcl commands that login to a SQL Server, pass SQL code, read results, etc. Sybtcl was inspired by similar tools written for Perl (sybperl, oraperl) but was written from scratch instead of borrowing on the work of either Perl extension. requires: Sybase Open Client (DB-Library), Sybase SQL Server discussion: comp.lang.tcl author: Tom Poindexter how to get: ftp tcl/extensions/sybtcl-2.2.tar.gz from ftp.aud.alcatel.com updated: 1994/11/04 name: tclgdbm version: 1.0 interface from: TCL interface to: gdbm description: none provided discussion: comp.lang.tcl author: Tuan Doan how to get: ftp pub/tcl/extensions/tclgdbm1.0* from harbor.ecn.purdue.edu updated: 1994/02/08 name: tcl+gdbm version: 0.1 interface from: TCL interface to: gdbm description: none provided discussion: comp.lang.tcl author: Christian Lindig how to get: ftp pub/local/sw/tcl+gdbm-0.1.tar.gz from ftp.ips.cs.tu-bs.de updated: 1994/05/04 name: Uniperl version: ? interface from: perl interface to: Unify 5.0 descritpion: Uniperl is a set of user subroutines to enable Perl programs to access Unify databases. requires: Perl 3.027 or higher, ? discussion: perldb-interest-REQUEST@vix.com author: Rick Wargo how to get: ftp pub/perl/db/uniperl/? from ftp.demon.co.uk updated: ? name: Willow version: 2.2 interface from: user interface to: WWW/Mosaic, Z39.50, ZDist (formerly free-WAIS) from CNIDR description: Willow (Washington Information Looker-upper Layered Over Windows) is a general purpose information retrieval tool. It provides a single, easy-to-use graphical user interface (X Windows / Motif) to any number of text-based bibliographic databases. references: http://www.cac.washington.edu/willow/home.html ports: DEC/Ultrix, Solaris, SunOS, RS6000/AIX. contact: willow@cac.washington.edu how to get: ftp willow/* from ftp.cac.washington.edu updated: 1994/06/30 --------------------------------------------------------------------------- --------------------------- other ----------------------------------------- --------------------------------------------------------------------------- name: "A Guide to the SQL standard" what: BNF SQL grammer version: ? description: A BNF grammer for SQL is included in the book. how to get: buy the book: "A Guide to the SQL standard" by Hugh Darwen and C.J. Date. updated: ? name: CDF (Common Data Format) what: data exchange library version: ? interfaces: ? access methods: ? distributed: ? query language: ? limits: ? robustness: ? description: A library and toolkit for multi-dimensional data sets. The basic component of CDF is a software programming interface that is a device independent view of the CDF data model requires: ? ports: ? restrictions: ? contact: ? how to get: ftp cdf.dir/* from nssdca.gsfc.nasa.gov. The CDF library to provide applications access to remote CDF datasets, can be obtained from its author: Hillel Steinberg . updated: ? name: examples from: "Information Retrieval, Data Structures & Algorithms," William B. Frakes, Ricardo Baeza-Yates, Editors, Prentice Hall, Englewood Cliffs, New Jersey 07632, 1992, ISBN 0-13-463837-9. what: example database code version: ? descriptions: example code from the book "Information Retrieval, Data Structures & Algorithms" how to get: ftp pub/reuse/ircode.tar.Z from ftp.vt.edu author: [resumably William B. Frakes, Ricardo Baeza-Yates] updated: ? name: _lex & yacc_ by Levine, Mason & Brown published by O'Reilly what: SQL yacc grammer version: ? parts: grammar description: In _lex & yacc_, by Levine, Mason & Brown an SQL parser is included as an example grammar author: Levine, Mason & Brown how to get: buy the book, or ftp published/oreilly/nutshell/lexyacc/? from ftp.uu.net. updated: ? name: MultiCal what: database date manipulation library version: 1.0 interfaces: ? access methods: ? multiuser: no transactions: no distributed: no query language: enhanced SQL2 limits: ? description: MultiCal is both a novel approach to supporting multiple calendars and internationalization of time constants and a query processor prototype that demonstrates this approach. MultiCal consists of about 48K source lines of C code; the query processor prototype consists of about 63K source lines of code. The documentation consists of fifteen documents, comprising some 300 pages of material. MultiCal consists of an approach to providing limited extensibility for support of multiple calendars and languages for temporal support within a database management system (DBMS). We have augmented the Structured Query Language (SQL), specifically, SQL2, with time values, i.e., temporal constants. Our approach is notable in that we allow many different calendars to be used in the database management system, and we incorporate only calendar-independent constructs into the language. We introduce three new temporal data types. New language features are defined for temporal built-in functions, special time values, arithmetic expressions involving time, temporal predicates, and aggregate functions over time. Ten languages are supported. To illustrate how an existing DBMS could be augmented to support multiple calendars, we provide a prototype DBMS that supports the proposed extensions. This prototype consists of query analysis and execution components. It eschews traditional functionality such as concurrency control and disk access methods, as these aspects are not relevant to timestamp management. ports: Sun4 contact: or Rick Snodgrass how to get: ftp tsql/multical/* from ftp.cs.arizona.edu updated: 1993/10/30 name: persist++ what: C++ object marshal/demarshal library version: 0.2 interfaces: C++ access methods: none robustness: ? description: Persist++ is a set of serialize/materialize/marshal routines that make it easy to store C++ objects to files or to send them across the network. author: Herman Moons how to get: ftp pub/impulse/persist++_0.2.tar.Z from ftp.cs.kuleuven.ac.be updated: 1994/08/16 name: SQL parser ? what: SQL yacc grammer ? version: ? description: ? author: Bruce Ring <73172.735@compuserve.com> how to get: wait for it to be posted to a comp.sources group updated: 1994/11/04 name: SQL-86 in HTML what: html version of some of the SQL-86 standard references: http://case50.ncsl.nist.gov/sql-86/ author: David Flater updated: 1994/12/30 From owner-freebsd-ports Fri Aug 25 22:25:14 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id WAA20394 for ports-outgoing; Fri, 25 Aug 1995 22:25:14 -0700 Received: from idiom.com (idiom.com [140.174.82.4]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id WAA20375 ; Fri, 25 Aug 1995 22:25:10 -0700 Received: (from muir@localhost) by idiom.com (8.6.11/8.6.10) id WAA16566; Fri, 25 Aug 1995 22:25:07 -0700 Date: Fri, 25 Aug 1995 22:25:07 -0700 From: David Muir Sharnoff Message-Id: <199508260525.WAA16566@idiom.com> To: maher@azstarnet.com Subject: Re: Boca multiport card Cc: ports@freebsd.org, questions@freebsd.org, v@idiom.com Sender: ports-owner@freebsd.org Precedence: bulk * Does anybody know if Boca 16 ports card would work with freebsd 2.0.5 ? and * can you use two of them? instad of terminal server, please include a hint * how to configuer the server and the modems with them This should be documented somewhere... This is how I have one 16-port boca board configured. Works fine. Unfortunantly the sio driver doesn't take advantage of the boca's interrupt register and so it polls all 16 ports every time any of the interrupts. I tried to fix the driver, but it kept hanging. The NetBSD driver does the right thing (I wrote the first version), but that doesn't help much. I don't know if you can run two of them on the same FreeBSD system. Because of the driver problem, I'm figuring that if I want that many serial ports I'll dedicate a machine to being a terminal server and run NetBSD on it. In every other respect, I find FreeBSD easier to deal with. (Or I did when I ran 2.0. 2.0.5 crashes way too often) -Dave device sio4 at isa? port 0x100 tty flags 0x1305 device sio5 at isa? port 0x108 tty flags 0x1305 device sio6 at isa? port 0x110 tty flags 0x1305 device sio7 at isa? port 0x118 tty flags 0x1305 device sio8 at isa? port 0x120 tty flags 0x1305 device sio9 at isa? port 0x128 tty flags 0x1305 device sio10 at isa? port 0x130 tty flags 0x1305 device sio11 at isa? port 0x138 tty flags 0x1305 device sio12 at isa? port 0x140 tty flags 0x1305 device sio13 at isa? port 0x148 tty flags 0x1305 device sio14 at isa? port 0x150 tty flags 0x1305 device sio15 at isa? port 0x158 tty flags 0x1305 device sio16 at isa? port 0x160 tty flags 0x1305 device sio17 at isa? port 0x168 tty flags 0x1305 device sio18 at isa? port 0x170 tty flags 0x1305 device sio19 at isa? port 0x178 tty flags 0x1305 irq 5 vector siointr From owner-freebsd-ports Fri Aug 25 23:02:40 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id XAA22070 for ports-outgoing; Fri, 25 Aug 1995 23:02:40 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id XAA22062 for ; Fri, 25 Aug 1995 23:02:38 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id XAA02811; Fri, 25 Aug 1995 23:02:31 -0700 Date: Fri, 25 Aug 1995 23:02:31 -0700 Message-Id: <199508260602.XAA02811@silvia.HIP.Berkeley.EDU> To: faulkner@mpd.tandem.com CC: ports@freebsd.org In-reply-to: <9508142046.AA10716@olympus> (faulkner@mpd.tandem.com) Subject: Re: port of astrolog 5.0 in incoming From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * astrolog50.port.tar.gz is in incoming. I can fetch the file and build. Thanks, I couldn't get to the MASTER_SITE in the Makefile so I used Andrey's site instead. I also added some extra rules and an install script to install Helpfile.500 and print out messages about it. Satoshi From owner-freebsd-ports Sat Aug 26 00:01:53 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA24282 for ports-outgoing; Sat, 26 Aug 1995 00:01:53 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA24276 for ; Sat, 26 Aug 1995 00:01:51 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id AAA03013; Sat, 26 Aug 1995 00:01:30 -0700 Date: Sat, 26 Aug 1995 00:01:30 -0700 Message-Id: <199508260701.AAA03013@silvia.HIP.Berkeley.EDU> To: erich@lodgenet.com CC: ports@freebsd.org In-reply-to: <199508141405.JAA21661@jake.lodgenet.com> (erich@lodgenet.com) Subject: Re: port of sudo From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * here's a port I threw together 'cause I've * gotten used to sudo and didn't find it. Thanks, I tried it. I made some changes (/etc/sudoers -> /usr/local/etc/sudoers, etc.) but there seems to be something wrong with the way it parses the sudoers file. For example: Cmnd_Alias SHELLS=/bin/sh,/bin/csh,/usr/local/bin/tcsh,/usr/local/bin/bash asami ALL=ALL,!SHELLS will make me execute tcsh and bash but not sh or csh.... I put the updated port in ftp://ftp.freebsd.org/pub/FreeBSD/incoming/sudo.tar.gz Can you (or someone else) please check it out? Satoshi From owner-freebsd-ports Sat Aug 26 00:08:51 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA24412 for ports-outgoing; Sat, 26 Aug 1995 00:08:51 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA24406 ; Sat, 26 Aug 1995 00:08:49 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id AAA03048; Sat, 26 Aug 1995 00:08:40 -0700 Date: Sat, 26 Aug 1995 00:08:40 -0700 Message-Id: <199508260708.AAA03048@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: erich@lodgenet.com, ports@freebsd.org, davidg@freebsd.org In-reply-to: <4728.809174181@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: ical 1.9 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * Do you want me to spam thud down to the metal? Would it help? I appreciate your concern.... ;) * You're free to have whatever done to that machine you feel is most * conducive to your work! I think what we need now is a machine that is running 2.1-stable, so if you can pull out all the cables, newfs all the disks, wipe the monitor, and install 2.1-stable from scratch, that would be great. I guess installing 0726-SNAP and running a "make world" on the stable /usr/src will be the easiest thing to do. However, I have a question for David: are you going to pull in the xdr_* changes to libc? If so, the libc version number will be bumped, so we probably want to wait until that is done (which will be soon if it is going to be, I guess, given the rush of commits coming from David lately...:)... Satoshi From owner-freebsd-ports Sat Aug 26 00:14:39 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA24554 for ports-outgoing; Sat, 26 Aug 1995 00:14:39 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA24548 for ; Sat, 26 Aug 1995 00:14:38 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.11/8.6.5) with ESMTP id AAA12794; Sat, 26 Aug 1995 00:13:34 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id AAA15830; Sat, 26 Aug 1995 00:15:31 -0700 Message-Id: <199508260715.AAA15830@corbin.Root.COM> To: asami@cs.berkeley.edu (Satoshi Asami) cc: jkh@time.cdrom.com, erich@lodgenet.com, ports@freebsd.org Subject: Re: ical 1.9 In-reply-to: Your message of "Sat, 26 Aug 95 00:08:40 PDT." <199508260708.AAA03048@silvia.HIP.Berkeley.EDU> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 26 Aug 1995 00:15:27 -0700 Sender: ports-owner@freebsd.org Precedence: bulk >However, I have a question for David: are you going to pull in the >xdr_* changes to libc? If so, the libc version number will be bumped, >so we probably want to wait until that is done (which will be soon if >it is going to be, I guess, given the rush of commits coming from >David lately...:)... Hey, give me enough time and I can destroy the world. :-) I thought briefly about the xdr changes. I skipped over them out of concern for it affecting our exsting ports. Do we really need to bump the library revision? We haven't officially released libc.so.2.1 yet, so I don't see the need. Everything built with a "libc.so.2.1" should be forward compatible. ...please advise. -DG From owner-freebsd-ports Sat Aug 26 00:27:57 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA25294 for ports-outgoing; Sat, 26 Aug 1995 00:27:57 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA25281 for ; Sat, 26 Aug 1995 00:27:54 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id AAA03148; Sat, 26 Aug 1995 00:27:48 -0700 Date: Sat, 26 Aug 1995 00:27:48 -0700 Message-Id: <199508260727.AAA03148@silvia.HIP.Berkeley.EDU> To: davidg@Root.COM CC: ports@freebsd.org In-reply-to: <199508260715.AAA15830@corbin.Root.COM> (message from David Greenman on Sat, 26 Aug 1995 00:15:27 -0700) Subject: Re: ical 1.9 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * I thought briefly about the xdr changes. I skipped over them out * of concern for it affecting our exsting ports. Do we really need to * bump the library revision? We haven't officially released * libc.so.2.1 yet, so I don't see the need. Everything built with a ^^^ 2.2, right? libc.so.2.1 went out with 2.0.5R.... * "libc.so.2.1" should be forward compatible. I'm not sure what your concern here is. It doesn't matter either way for us (the ports team). We will rebuild the whole ports tree on a 2.1-ALPHA (or something close to it) machine before the release anyway. All I know is that we can't ship packages using libc.so.2.1 if the bindist has libc.so.2.2, or the other way around. Whatever you decide to do, that's fine for us, as long as we are consistent with our own version number policies. My only request is that if you are going to make this change, please do it soon, that will make it easier for us (and harder to screw up). Satoshi From owner-freebsd-ports Sat Aug 26 00:47:06 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA26773 for ports-outgoing; Sat, 26 Aug 1995 00:47:06 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA26765 for ; Sat, 26 Aug 1995 00:47:04 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id AAA03244; Sat, 26 Aug 1995 00:46:56 -0700 Date: Sat, 26 Aug 1995 00:46:56 -0700 Message-Id: <199508260746.AAA03244@silvia.HIP.Berkeley.EDU> To: A.C.P.M.Kalker@student.utwente.nl CC: jkh@time.cdrom.com, ports@freebsd.org In-reply-to: (message from Alain Kalker on Sat, 26 Aug 1995 03:18:21 +0200 (MET DST)) Subject: Re: New port for slirp From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * > I don't mind at all! Go right ahead and update it.. Thanks, updated! * - configure says there is an option to not compile ppp support into the * program. I don't know if this is sufficient reason to make the port * interactive to ask the user about it, so I left it as it is. Yeah, I think that's ok. It's not like it's not going to run without ppp, right? * - The second URL in the documentation (ftp://freedom.wit.com:...) seems to * be no longer valid (directory does not exist anymore). I have no idea on this one, whatever you say is fine.... Satoshi From owner-freebsd-ports Sat Aug 26 00:58:16 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA27482 for ports-outgoing; Sat, 26 Aug 1995 00:58:16 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA27476 for ; Sat, 26 Aug 1995 00:58:14 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id AAA03290; Sat, 26 Aug 1995 00:58:07 -0700 Date: Sat, 26 Aug 1995 00:58:07 -0700 Message-Id: <199508260758.AAA03290@silvia.HIP.Berkeley.EDU> To: dfk@wildcat.cs.dartmouth.edu CC: ports@freebsd.org In-reply-to: <199508260026.UAA24650@wildcat.cs.dartmouth.edu> (dfk@wildcat.cs.dartmouth.edu) Subject: Re: INDEX in FreeBSD/ports-2.0/ From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * The INDEX file in * ftp://ftp.freebsd.org/pub/FreeBSD/ports-2.0/ * is out of date. Could you please update it? What do you mean by out of date? I think it is pretty up-to-date with respect to the directory it represents, i.e., the ports-2.0 tree.... Satoshi From owner-freebsd-ports Sat Aug 26 01:34:24 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id BAA29434 for ports-outgoing; Sat, 26 Aug 1995 01:34:24 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id BAA29416 ; Sat, 26 Aug 1995 01:34:22 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id BAA03390; Sat, 26 Aug 1995 01:34:19 -0700 Date: Sat, 26 Aug 1995 01:34:19 -0700 Message-Id: <199508260834.BAA03390@silvia.HIP.Berkeley.EDU> To: jkh@freefall.FreeBSD.org CC: ports@freefall.FreeBSD.org, Thomas Graichen In-reply-to: <199508231338.GAA03257@freefall.FreeBSD.org> (jkh@freefall.FreeBSD.org) Subject: Re: cvs commit: ports/net/Mosaic - Imported sources From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@FreeBSD.org Precedence: bulk * Bring in a port of Mosaic. This can only be built by people with Motif, * so we'll not enable it by default. I was thinking about (ok, not my idea) adding a NEED_MOTIF variable for this. There is another port in the same boat (audio/xmcd). In fact, if someone can help us (Thomas, are you still interested), maybe we can modify the ports framework to handle Motif ports and start adding more. Other than adding a test for NEED_MOTIF, we probably want to make it possible to build packages with either static or dynamic Motif libraries. I'm not sure how to go about this.... Well, what do you think? Satoshi From owner-freebsd-ports Sat Aug 26 02:25:45 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id CAA03305 for ports-outgoing; Sat, 26 Aug 1995 02:25:45 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id CAA03299 ; Sat, 26 Aug 1995 02:25:40 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id CAA05181; Sat, 26 Aug 1995 02:25:38 -0700 Date: Sat, 26 Aug 1995 02:25:38 -0700 Message-Id: <199508260925.CAA05181@silvia.HIP.Berkeley.EDU> To: paul@freebsd.org CC: ports@freebsd.org In-reply-to: <199508251300.OAA16567@server.netcraft.co.uk> (message from Paul Richards on Fri, 25 Aug 1995 14:00:39 +0100 (BST)) Subject: Re: Dependencies From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * I don't like the way dependencies currently work. * * I want to build ghostview but it depends on ghostscript so when I try * and compile it it first goes off to get ghostscript and builds that, * but I've already got ghostscript installed! * * Can't the dependencies use pkg_* in some way to see if the package already * exists before trying to rebuild it again? Uhh, it should. The line: EXEC_DEPENDS= gs:${PORTSDIR}/print/ghostscript in the ghostview Makefile does exactly that, check if the program "gs" is in the search path (it uses "which"), and goes to build ghostscript only if it's not found. Maybe you don't have /usr/local/bin in your root's search path, then well sorry, it won't work, and I don't see any workaround for it. Satoshi From owner-freebsd-ports Sat Aug 26 02:33:20 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id CAA03703 for ports-outgoing; Sat, 26 Aug 1995 02:33:20 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id CAA03697 ; Sat, 26 Aug 1995 02:33:17 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id CAA05289; Sat, 26 Aug 1995 02:33:15 -0700 Date: Sat, 26 Aug 1995 02:33:15 -0700 Message-Id: <199508260933.CAA05289@silvia.HIP.Berkeley.EDU> To: paul@freebsd.org CC: ports@freebsd.org In-reply-to: <199508251259.NAA16555@server.netcraft.co.uk> (message from Paul Richards on Fri, 25 Aug 1995 13:59:56 +0100 (BST)) Subject: Re: msql From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * "Commercial purposes" is defined within the scope of this license as * the generation of monetary revenue from the redistribution of the * software or modified versions of the software, beit by itself or * "bundled" with or incorporated into any other product. Generation of * revenue via the use of this software is not considered a "commercial purpose". Duh. You're right, I'll add it to ports/LEGAL. Thanks.... * I also ran into a little quirk in that mtree doesn't build the top level * directory for the package and if I change that tope-level directory during * configuration then mtree still looks for the default location. I can't understand this one. Can you elaborate? Satoshi From owner-freebsd-ports Sat Aug 26 03:03:54 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id DAA06168 for ports-outgoing; Sat, 26 Aug 1995 03:03:54 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id DAA06162 ; Sat, 26 Aug 1995 03:03:51 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id DAA25972; Sat, 26 Aug 1995 03:03:43 -0700 To: asami@cs.berkeley.edu (Satoshi Asami) cc: jkh@freefall.FreeBSD.org, ports@freefall.FreeBSD.org, Thomas Graichen Subject: Re: cvs commit: ports/net/Mosaic - Imported sources In-reply-to: Your message of "Sat, 26 Aug 1995 01:34:19 PDT." <199508260834.BAA03390@silvia.HIP.Berkeley.EDU> Date: Sat, 26 Aug 1995 03:03:43 -0700 Message-ID: <25970.809431423@time.cdrom.com> From: "Jordan K. Hubbard" Sender: ports-owner@FreeBSD.org Precedence: bulk > * Bring in a port of Mosaic. This can only be built by people with Motif, > * so we'll not enable it by default. > > I was thinking about (ok, not my idea) adding a NEED_MOTIF variable > for this. There is another port in the same boat (audio/xmcd). I think that's a fine idea! I'm still waiting for some feedback on my README proposal, mind you, but that's just FINE. We can discuss Motif first if you wish! :-) Jordan From owner-freebsd-ports Sat Aug 26 03:07:12 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id DAA06545 for ports-outgoing; Sat, 26 Aug 1995 03:07:12 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id DAA06532 ; Sat, 26 Aug 1995 03:07:08 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id DAA00685; Sat, 26 Aug 1995 03:06:42 -0700 Date: Sat, 26 Aug 1995 03:06:42 -0700 Message-Id: <199508261006.DAA00685@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: jkh@freefall.FreeBSD.org, ports@freefall.FreeBSD.org, graichen@omega.physik.fu-berlin.de In-reply-to: <25970.809431423@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: cvs commit: ports/net/Mosaic - Imported sources From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@FreeBSD.org Precedence: bulk * > I was thinking about (ok, not my idea) adding a NEED_MOTIF variable * > for this. There is another port in the same boat (audio/xmcd). * * I think that's a fine idea! * * I'm still waiting for some feedback on my README proposal, mind you, * but that's just FINE. We can discuss Motif first if you wish! :-) Well, that was not a new idea, I just threw out what I already had. ;) About the README thing...well ok, I'll reply to it now...although I'm not sure how it will work, maybe we can all discuss it together. Satoshi From owner-freebsd-ports Sat Aug 26 03:32:44 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id DAA08482 for ports-outgoing; Sat, 26 Aug 1995 03:32:44 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id DAA08473 for ; Sat, 26 Aug 1995 03:32:39 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id DAA01272; Sat, 26 Aug 1995 03:32:29 -0700 Date: Sat, 26 Aug 1995 03:32:29 -0700 Message-Id: <199508261032.DAA01272@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: ports@freebsd.org In-reply-to: <3688.808924626@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: `make info'? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * I think it's finally come to pass that we have too many ports.. :-) There are now 342 ports.... ;) * I think it's time that we considered this, and I have two quick * suggestions just off the top of my head (there may be better ones of * course): * * 1. Build an auto-generated README file at each level of the tree that's * *human readable* as well as the INDEX at the top (which, someday RSN, * I'll write a utility for actually using :-). BTW Jordan, INDEX is now used to auto-generate the "ports home page", i.e., http://www.freebsd.org/Ports. Very useful. Anyway, adding a README to each category is a good idea. I think this can be separated into two parts, the description of the category and that of individual ports. To auto-generate this README, we can create a subdirectory "pkg" that has COMMENT and DESCR (I have no idea what PLIST here can do ;). For instance, the emulators/README will look like this: === This is the README file of ports/emulators. (taken from template) This category contains programs that you can use to run programs for different operating systems and those you can use to read/write data written in their format. (taken from pkg/DESCR) These are the one-line descriptions of each port: (taken from template) cpmemu: Cpm emulator version 0.2 cpmtools: Utility to transfer files from/to CP/M (R) diskettes. hfs: hfs - program for reading Macintosh HFS floppy disks, hard drives a. mtools: Mtools - a collection of tools for manipulating MSDOS files. Vers. pcemu: pcemu - An 8086 PC emulator, written by By David Hedley (hedley@cs.. tkfhs: tkhfs - a Tcl/Tk front end to the hfs program. vmsbackup: VMSBACKUP reads VMS BACKUP tapes. (obviously taken from */pkg/COMMENT -- I truncated long lines) If you want to see a more detailed description of each port, please cd into that directory and type "make info". (taken from template) === And port/README will have a little more "meta" version of this, taking emulators/pkg/COMMENT and such. Obviously, it needs a separate template too. * 2. Add another target called `info' or something suitably mnemonic to * the ports structure so that the user can type `make info' at any level * of the tree to get a human readable dump of what's there. Document * this option, along with other useful ones like `all' and `install' * (we should never assume that the user just knows what to do), in a * top level README and hope that the user is at least reasonable enough * to read that first. I think this is a good idea. Actually, for the top level and one level below it, I think we can just have it "cat README".... :) Speaking of the toplevel, may I delete GUIDELINES? It is obsolete, I have no intentions (nor the time) to update it, people should refer to the handbook anyway.... Satoshi From owner-freebsd-ports Sat Aug 26 04:20:06 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id EAA12902 for ports-outgoing; Sat, 26 Aug 1995 04:20:06 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id EAA12896 ; Sat, 26 Aug 1995 04:20:03 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id EAA01925; Sat, 26 Aug 1995 04:20:01 -0700 Date: Sat, 26 Aug 1995 04:20:01 -0700 Message-Id: <199508261120.EAA01925@silvia.HIP.Berkeley.EDU> To: torstenb@freebsd.org CC: ports@freebsd.org Subject: patch for bsd.port.mk From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk This is a patch to make bsd.port.mk handle bad master sites. The old one assumes that ncftp returns 0 only when the fetch has succeeded, which is not true depending on its version. It actually cleaned up the source a bit, as you can see. Note this is for the -stable tree, you need to edit it manually if you are running -current tree. Satoshi ======= diff -ur /s/usr/src/share/mk/bsd.port.mk ./bsd.port.mk --- /s/usr/src/share/mk/bsd.port.mk Tue Jun 6 03:56:34 1995 +++ ./bsd.port.mk Sat Aug 26 03:53:44 1995 @@ -421,34 +421,32 @@ ${ECHO_MSG} ">> $$file doesn't seem to exist on this system."; \ for site in ${MASTER_SITES}; do \ ${ECHO_MSG} ">> Attempting to fetch from $${site}"; \ - if ${NCFTP} ${NCFTPFLAGS} $${site}$${file}; then \ - break; \ + (${NCFTP} ${NCFTPFLAGS} $${site}$${file} || true); \ + if [ -f $$file -o -f `basename $$file` ]; then \ + continue 2; \ fi \ done; \ - if [ ! -f $$file -a ! -f `basename $$file` ]; then \ - ${ECHO_MSG} ">> Couldn't fetch it - please try to retreive this";\ - ${ECHO_MSG} ">> port manually into ${DISTDIR} and try again."; \ - exit 1; \ - fi; \ + ${ECHO_MSG} ">> Couldn't fetch it - please try to retreive this";\ + ${ECHO_MSG} ">> port manually into ${DISTDIR} and try again."; \ + exit 1; \ fi \ done) .if defined(PATCHFILES) @if [ ! -d ${PATCHDIST} ]; then mkdir -p ${PATCHDIST}; fi @(cd ${PATCHDIST}; \ for file in ${PATCHFILES}; do \ - if [ ! -f $$file -a ! -f `basename $$file` ]; then \ + if [ -f $$file -o -f `basename $$file` ]; then \ ${ECHO_MSG} ">> $$file doesn't seem to exist on this system."; \ for site in ${PATCH_SITES}; do \ ${ECHO_MSG} ">> Attempting to fetch from $${site}."; \ - if ${NCFTP} ${NCFTPFLAGS} $${site}$${file}; then \ - break; \ + (${NCFTP} ${NCFTPFLAGS} $${site}$${file} || true); \ + if [ ! -f $$file -a ! -f `basename $$file` ]; then \ + continue 2; \ fi \ done; \ - if [ ! -f $$file -a ! -f `basename $$file` ]; then \ - ${ECHO_MSG} ">> Couldn't fetch it - please try to retreive this";\ - ${ECHO_MSG} ">> port manually into ${PATCHDIST} and try again."; \ - exit 1; \ - fi; \ + ${ECHO_MSG} ">> Couldn't fetch it - please try to retreive this";\ + ${ECHO_MSG} ">> port manually into ${PATCHDIST} and try again."; \ + exit 1; \ fi \ done) .endif From owner-freebsd-ports Sat Aug 26 04:31:21 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id EAA13445 for ports-outgoing; Sat, 26 Aug 1995 04:31:21 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id EAA13439 for ; Sat, 26 Aug 1995 04:31:19 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id EAA28774; Sat, 26 Aug 1995 04:31:13 -0700 To: asami@cs.berkeley.edu (Satoshi Asami) cc: ports@freebsd.org Subject: Re: `make info'? In-reply-to: Your message of "Sat, 26 Aug 1995 03:32:29 PDT." <199508261032.DAA01272@silvia.HIP.Berkeley.EDU> Date: Sat, 26 Aug 1995 04:31:13 -0700 Message-ID: <28772.809436673@time.cdrom.com> From: "Jordan K. Hubbard" Sender: ports-owner@freebsd.org Precedence: bulk > I think this is a good idea. Actually, for the top level and one > level below it, I think we can just have it "cat README".... :) Yes! Yes! > Speaking of the toplevel, may I delete GUIDELINES? It is obsolete, I > have no intentions (nor the time) to update it, people should refer to > the handbook anyway.... Assuming that we replace it with a system like this, I have no objection. Jordan From owner-freebsd-ports Sat Aug 26 04:34:41 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id EAA13652 for ports-outgoing; Sat, 26 Aug 1995 04:34:41 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id EAA13642 for ; Sat, 26 Aug 1995 04:34:40 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id EAA02000; Sat, 26 Aug 1995 04:34:32 -0700 Date: Sat, 26 Aug 1995 04:34:32 -0700 Message-Id: <199508261134.EAA02000@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: ports@freebsd.org In-reply-to: <28772.809436673@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: `make info'? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@freebsd.org Precedence: bulk * > Speaking of the toplevel, may I delete GUIDELINES? It is obsolete, I * > have no intentions (nor the time) to update it, people should refer to * > the handbook anyway.... * * Assuming that we replace it with a system like this, I have no * objection. Uhh, GUIDELINES was for porters, not users...so this system is not going to "replace" it.... Satoshi From owner-freebsd-ports Sat Aug 26 04:51:52 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id EAA14236 for ports-outgoing; Sat, 26 Aug 1995 04:51:52 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id EAA14230 for ; Sat, 26 Aug 1995 04:51:50 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id EAA28902; Sat, 26 Aug 1995 04:51:44 -0700 To: asami@cs.berkeley.edu (Satoshi Asami) cc: ports@freebsd.org Subject: Re: `make info'? In-reply-to: Your message of "Sat, 26 Aug 1995 04:34:32 PDT." <199508261134.EAA02000@silvia.HIP.Berkeley.EDU> Date: Sat, 26 Aug 1995 04:51:44 -0700 Message-ID: <28899.809437904@time.cdrom.com> From: "Jordan K. Hubbard" Sender: ports-owner@freebsd.org Precedence: bulk > Uhh, GUIDELINES was for porters, not users...so this system is not > going to "replace" it.... You misunderstand me. If you're going to go to a "meta README" deal, then you're going to have a chance to do more than talk about invoking rules like `info' (and `build' and `install', please!), you'll be able to point to the URL of the ports guidelines section of the handbook. Those so inclined can follow it. Problem solved. In fact, while we're at it, why not also do the README in HTML? It'd still be human readable if you were careful about imbeding the formatting statements unobtrusively (no AREFs in the middle of paragraphs, just down in a summary bar on the bottom of the page). Then we can automate a little CGI tree-walker for the ports directly from the web. Jordan From owner-freebsd-ports Sat Aug 26 05:49:47 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id FAA17330 for ports-outgoing; Sat, 26 Aug 1995 05:49:47 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id FAA17324 for ; Sat, 26 Aug 1995 05:49:46 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id FAA02620; Sat, 26 Aug 1995 05:49:38 -0700 Date: Sat, 26 Aug 1995 05:49:38 -0700 Message-Id: <199508261249.FAA02620@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: ache@astral.msk.su, ports@freefall.FreeBSD.org In-reply-to: <28857.809437580@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: cvs commit: ports/utils/astrolog Makefile From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@FreeBSD.org Precedence: bulk * Hey! I got it! Let's wimp out and go for a ports/misc - all the * stuff we can't figure out how to classify! :-) Yeah! I agree with this one...and probably the whole utils/ subdirectory should move here too. Now I know why I was feeling so funny about this category, everything is a utility in some sense so the utils/ category was really just a "misc".... And for "occult"...well I still like that name but seems like we are the minority, Andrey. But I understand that it may offend or be misunderstood by some people, so I'd rather play it safe here. Satoshi From owner-freebsd-ports Sat Aug 26 10:12:31 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id KAA24075 for ports-outgoing; Sat, 26 Aug 1995 10:12:31 -0700 Received: from misery.sdf.com (misery.sdf.com [204.191.196.34]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id KAA24069 for ; Sat, 26 Aug 1995 10:12:29 -0700 Received: by misery.sdf.com id <1133>; Sat, 26 Aug 1995 10:08:19 +0100 Date: Sat, 26 Aug 1995 10:08:07 -0700 (PDT) From: Tom Samplonius To: David Kotz cc: ports@FreeBSD.org Subject: Re: INDEX in FreeBSD/ports-2.0/ In-Reply-To: <199508260026.UAA24650@wildcat.cs.dartmouth.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ports-owner@FreeBSD.org Precedence: bulk On Fri, 25 Aug 1995, David Kotz wrote: > The INDEX file in > ftp://ftp.freebsd.org/pub/FreeBSD/ports-2.0/ > is out of date. Could you please update it? That is no longer being maintained. Use ftp://ftp.freebsd.org/pub/FreeBSD-current/ports Tom From owner-freebsd-ports Sat Aug 26 12:21:11 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id MAA27221 for ports-outgoing; Sat, 26 Aug 1995 12:21:11 -0700 Received: from jolt.eng.umd.edu (jolt.eng.umd.edu [129.2.102.5]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id MAA27215 ; Sat, 26 Aug 1995 12:21:09 -0700 Received: from cappuccino.eng.umd.edu (cappuccino.eng.umd.edu [129.2.98.14]) by jolt.eng.umd.edu (8.6.10/8.6.4) with ESMTP id PAA13279; Sat, 26 Aug 1995 15:21:06 -0400 Received: (chuckr@localhost) by cappuccino.eng.umd.edu (8.6.10/8.6.4) id PAA04332; Sat, 26 Aug 1995 15:21:05 -0400 Date: Sat, 26 Aug 1995 15:21:05 -0400 (EDT) From: Chuck Robey To: Satoshi Asami cc: paul@freebsd.org, ports@freebsd.org Subject: Re: Dependencies In-Reply-To: <199508260925.CAA05181@silvia.HIP.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ports-owner@freebsd.org Precedence: bulk On Sat, 26 Aug 1995, Satoshi Asami wrote: > * I don't like the way dependencies currently work. > * > * I want to build ghostview but it depends on ghostscript so when I try > * and compile it it first goes off to get ghostscript and builds that, > * but I've already got ghostscript installed! > * > * Can't the dependencies use pkg_* in some way to see if the package already > * exists before trying to rebuild it again? > > Uhh, it should. The line: > > EXEC_DEPENDS= gs:${PORTSDIR}/print/ghostscript > > in the ghostview Makefile does exactly that, check if the program "gs" > is in the search path (it uses "which"), and goes to build ghostscript > only if it's not found. > > Maybe you don't have /usr/local/bin in your root's search path, then > well sorry, it won't work, and I don't see any workaround for it. Satoshi, the only time this is a pain for me is with libs. One easy example is the grpahics subdir, which always seems to rebuild the libs if the associated directory in ports/graphics doesn't contain the library in question. I am right now upgrading to current ports; has this been fixed there? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-ports Sat Aug 26 14:58:44 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id OAA03648 for ports-outgoing; Sat, 26 Aug 1995 14:58:44 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id OAA03641 for ; Sat, 26 Aug 1995 14:58:40 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id OAA06245; Sat, 26 Aug 1995 14:58:20 -0700 From: "Rodney W. Grimes" Message-Id: <199508262158.OAA06245@gndrsh.aac.dev.com> Subject: Re: ical 1.9 To: asami@cs.berkeley.edu (Satoshi Asami) Date: Sat, 26 Aug 1995 14:58:20 -0700 (PDT) Cc: davidg@Root.COM, ports@freebsd.org In-Reply-To: <199508260727.AAA03148@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Aug 26, 95 00:27:48 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1690 Sender: ports-owner@freebsd.org Precedence: bulk > > * I thought briefly about the xdr changes. I skipped over them out > * of concern for it affecting our exsting ports. Do we really need to > * bump the library revision? We haven't officially released > * libc.so.2.1 yet, so I don't see the need. Everything built with a > ^^^ > 2.2, right? libc.so.2.1 went out with 2.0.5R.... Satoshi is correct here, libc.so.2.1 was shipped with 2.0.5R, I just double checked the cdrom: usr/lib/libc.so.2.1 > * "libc.so.2.1" should be forward compatible. > > I'm not sure what your concern here is. It doesn't matter either way > for us (the ports team). We will rebuild the whole ports tree on a > 2.1-ALPHA (or something close to it) machine before the release > anyway. All I know is that we can't ship packages using libc.so.2.1 > if the bindist has libc.so.2.2, or the other way around. IMHO, we should pull the xdr changes in and bump the branch to libc.so.2.2, if we make additional libc changes in the main branch (HEAD) we will have to bump it to 2.3. > Whatever you decide to do, that's fine for us, as long as we are > consistent with our own version number policies. My only request is > that if you are going to make this change, please do it soon, that > will make it easier for us (and harder to screw up). This will mean that 2.0.5R -> 2.1 upgrade is going to be a bit harder, and require a bit more work. We did want to retain as much compatibility with 2.0.5R as possible, but, like usual, that has already been shot to pieces :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-ports Sat Aug 26 23:46:31 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id XAA10437 for ports-outgoing; Sat, 26 Aug 1995 23:46:31 -0700 Received: from phoenix.csie.nctu.edu.tw (phoenix.csie.nctu.edu.tw [140.113.17.171]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id XAA10431 for ; Sat, 26 Aug 1995 23:46:20 -0700 Received: from ccsun30.csie.nctu.edu.tw (jdli@ccsun30.csie.nctu.edu.tw [140.113.17.157]) by phoenix.csie.nctu.edu.tw (8.6.11/8.6.4) with SMTP id OAA19679 for ; Sun, 27 Aug 1995 14:46:15 +0800 From: jdli@csie.nctu.edu.tw (Chien-Ta Lee) Message-Id: <199508270646.OAA19679@phoenix.csie.nctu.edu.tw> Subject: port of xsysinfo-1.0 To: freebsd-ports@FreeBSD.ORG Date: Sun, 27 Aug 1995 14:45:14 +0800 (CST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 349 Sender: ports-owner@FreeBSD.ORG Precedence: bulk Hi : I had put my xsysinfo-1.0 at ftp://ftp.cdrom.com/pub/FreeBSD/incoming /port-xsysinfo-1.0.tgz Maybe someone can take a look at it, and put it into the port tree. Thanks. -- 李 建 達 (Adonis) 交大資工 Mail: jdli@csie.nctu.edu.tw