From owner-freebsd-questions Tue Aug 8 16:15:34 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 76A3337B830 for ; Tue, 8 Aug 2000 16:15:26 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA173030; Tue, 8 Aug 2000 19:15:10 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000808213136.24670.qmail@web4102.mail.yahoo.com> References: <20000808213136.24670.qmail@web4102.mail.yahoo.com> Date: Tue, 8 Aug 2000 19:15:49 -0400 To: John Johnson , freebsd-questions@FreeBSD.ORG, lprng@lprng.com From: Garance A Drosihn Subject: Re: Installing LPRng 3.6.22 and ifhp 3.3.19 Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:31 PM -0700 8/8/00, John Johnson wrote: >Garance, > >I did start there, but the version included in the >ports collection is 3.6.8; I thought I'd try with the >current version if possible. That is a reasonable thing to want to do. My point is that the PORT will probably give you several good clues as to what you need to do to get LPRng running. I don't mean "just blindly make the port", I mean "look at the port, the updates it applies, the makefile it uses, and the configuration options that it chooses". For most programs, the new version of a program will probably be "basically the same" as the old version, at least as far as porting-issues are concerned. So, the port itself is a good source of ideas for how to make the new version, even if the port is for an older version of the software. I am not an expert in ports, but what I like to do is a 'make checksum' for some port, at which point it has (generally) downloaded most of the interesting files. I then poke around in the 'patches' directory, or check to see what the makefile is doing. Sometimes I'll do a 'make configure', and then check to see what the port has created in the resulting 'work' directory. I didn't mean to seem like I was just blowing you off. I am just saying that the ports collection really IS a good first-place to look for tips on how to get some program to compile. You and I (and others on this list) could sit down and rediscover all the issues already discovered by the maintainer of the port, but what point is there in our redoing that person's work? --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message