From owner-freebsd-ports Sun Apr 19 21:40:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17114 for freebsd-ports-outgoing; Sun, 19 Apr 1998 21:40:57 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17081; Mon, 20 Apr 1998 04:40:45 GMT (envelope-from asami@vader.cs.berkeley.edu) Received: from baloon.mimi.com (sjx-ca124-36.ix.netcom.com [207.223.162.164]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id VAA09619; Sun, 19 Apr 1998 21:40:43 -0700 (PDT) Received: (from asami@localhost) by baloon.mimi.com (8.8.8/8.8.8) id VAA10469; Sun, 19 Apr 1998 21:40:38 -0700 (PDT) (envelope-from asami) Date: Sun, 19 Apr 1998 21:40:38 -0700 (PDT) Message-Id: <199804200440.VAA10469@baloon.mimi.com> To: brett@peloton.physics.montana.edu CC: ports@FreeBSD.ORG, jkh@FreeBSD.ORG In-reply-to: (message from Brett Taylor on Sun, 19 Apr 1998 19:15:34 -0600 (MDT)) Subject: Re: porting question regarding AfterStep-1.4.4 From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Hi all, Hi Brett, * I have a port of AfterStep-1.4.4 JUST about ready to go, but I've run into * a problem. The PLIST, due to the way AS does its configuration now, has * items in it that have "(" and ")" in their names. This doesn't seem to * cause any trouble during a make install, make deinstall, or pkg_delete. * However, it appears to have caused pkg_add to fail. The pkg_add process * starts just dandy and goes for awhile, then says "Syntax error - * unexpected '(' found" and although I can continue to hear the disk grind, * the actual copying of files appears to stop and the package does not get * registered. It's NOT just the files with "(" in them that don't get * installed either. Do I need to escape the parentheses w/ a "\" or * something? There are also items in the PLIST that have spaces in them - * does the same thing apply to them (although I've seen no errors concerning * them)? I believe Jordan will fix that in a nanosecond. :) * A second question - it's my feeling that since this is actually not a * release, but a development release that it shouldn't replace 1.0. There * are a few bits of 1.4.4 that are unstable (this may be due to my not * understanding the new configuration), but it's much more coherent and * stable than their 1.4 release. I do not think it's quite as stable as * 1.0. Can we have an afterstep-devel port and still keep the 1.0 port * around or should I just diff the 1.4.4 against the 1.0 port? They are * significantly different. I just did a repository copy to afterstep144. Please send in the patches with send-pr and someone will commit it. If you can make the patches relative to the x11/afterstep144 port, that will make the committer's job easier. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message