From owner-freebsd-questions Fri Oct 20 12:24:14 2000 Delivered-To: freebsd-questions@freebsd.org Received: from relay2.inwind.it (relay2.inwind.it [212.141.53.73]) by hub.freebsd.org (Postfix) with ESMTP id B932337B4D7 for ; Fri, 20 Oct 2000 12:24:07 -0700 (PDT) Received: from bartequi.ottodomain.org (62.98.153.52) by relay2.inwind.it (5.1.046) id 39CB09790070A481; Fri, 20 Oct 2000 21:20:09 +0200 From: Salvo Bartolotta Date: Fri, 20 Oct 2000 20:21:31 GMT Message-ID: <20001020.20213100@bartequi.ottodomain.org> Subject: Re: gnucash and odd port behavior To: j mckitrick Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <20001020114718.A44597@dogma.freebsd-uk.eu.org> References: <20001020114718.A44597@dogma.freebsd-uk.eu.org> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 10/20/00, 11:47:18 AM, j mckitrick wrote=20 regarding gnucash and odd port behavior: > I had some trouble building gnucash last night. I should mention I=20 recently > deleted my entire ports tree so I could start from scratch, and I used= =20 the > cvsup file to limit them to those that interest me. Maybe this is=20 what > caused my problem. The port won't build. First, D/Ling the package=20 didn't > work, tellingg me I was denied access to the file on the freebsd=20 server. > Then, when I tried a port instead of a package, the compile died. I=20 don't > have the error, but I can get it later tonight. I thought maybe=20 someone > would have some ideas first. Jonathon, The following "philological" information/approach may be unrelated to=20 your problem, but I think you will probably find this general=20 consideration useful per se. Whenever you update any source tree (src-all, ports-all, etc.), it is=20 safe practice to run a preliminary cvsup session using an appropriate=20 tag and/or date in the supfile. Actually, in this session, cvsup=20 creates the checkouts file reflecting the **initial** state of your=20 collection. Subsequent updates will be making use of=20 normal/standard/well-known supfiles. The spirit of the operation is illustrated by John Polstra himself in=20 the FAQ found at http://www.polstra.com (please have a look at them,=20 in particular Q12 and Q13). After reinstalling your ports tree, you should first cvsup ports using=20 a suitable date tag (cf cvsup(1)); that is, in the date tag in=20 question, you should specify a date close to that of "shipping" of=20 your ports tree. For all your subsequent updates, you'll be using the=20 normal supfile. The recipe, in short, is: **add** a suitable "date" tag to your=20 ports-supfile, as per the instructions in cvsup(1). HTH anyway, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message