From owner-freebsd-ports Thu Apr 13 16:26:49 2000 Delivered-To: freebsd-ports@freebsd.org Received: from stono.cs.cofc.edu (stono.cs.cofc.edu [153.9.17.3]) by hub.freebsd.org (Postfix) with ESMTP id 15A1D37BDE9 for ; Thu, 13 Apr 2000 16:26:43 -0700 (PDT) (envelope-from jimmy@cs.cofc.edu) Received: from [153.9.17.27] (burton.cs.cofc.edu [153.9.17.27]) by stono.cs.cofc.edu (8.9.3/8.9.3) with ESMTP id TAA11263 for ; Thu, 13 Apr 2000 19:24:22 -0400 X-Sender: jimmy@stono.cs.cofc.edu Message-Id: In-Reply-To: <01fb01bfa15f$3b2e0520$0200000a@weeble.dyndns.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 13 Apr 2000 19:27:36 -0400 To: freebsd-ports@freebsd.org From: "James B. Wilkinson" Subject: Re: Making a package from a port Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >----- Original Message ----- >> I built the python-1.5.2 port with one change from the configuration >> that it comes with: >> I changed WITH_TK? = yes to WITH_TK? = no. The port built ok, >> and none of the tests failed (although some were skipped, as expected). >> >> The next step is to copy this working python to about a dozen other >> machines in the same lab. It seemed to me that the right way to do that >> would be to make a package of the newly built port. >> So, thinking that I was >> following the instructions on FreeBSD.org's webpage, I typed, "make >> package" in /usr/ports/lang/python. It worked for a few seconds, and then >> quit because of an error. I'm sorry, I didn't write down the message >> exactly, but the jist of it was that tar couldn't find a file named >> "_tk.so >> >> That makes it seem to me as if it's trying to make a package of the >> standard port *with* tk rather than my modified one. >> >> I suspect that I might get it to work if I edited the PLIST file by hand, >> but I'm hoping that there's a more automated (and therefore probably more >> accurate) way to get what I want. Any chance? >> >> Thanks. >You hit the nail on the head. "make package" is using the PLIST to >determine what goes in that package. You're going to need to edit the >PLIST, then make your package. You'll only have to do this once, of course, >not on each machine. A question for the ports list: Would it be a good idea if the port facility were able to accommodate lines in the PLIST that were equivalent to #if (WITH_TK? == yes) include PLIST.tk and then put the names of all the tk-specific files in PLIST.tk? That would make it a lot easier on people who are building packages from ports with a different configuration. It seems clear that the ports are designed to be built that way if one wants to. Might make maintenance of a port easier, too? If that would be like asking for the moon from your point of view, just consider it mad ravings from the uninformed. BTW, I got it to work, but I had to edit work/PLIST and work/.PLIST.mktmp in addition to pkg/PLIST. Thanks ------------------------------------------------------------- Jimmy Wilkinson | Perfesser of Computer Science jimmy@cs.CofC.edu | The College of Charleston (843) 953-8160 | Charleston SC 29424 If there is one word to describe me, that word would have to be "profectionist". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message