Date: Thu, 13 Apr 2000 19:29:27 -0500 From: "Scot W. Hetzel" <hetzels@westbend.net> To: "James B. Wilkinson" <jimmy@CS.cofc.EDU> Cc: <freebsd-ports@FreeBSD.ORG> Subject: Re: Making a package from a port Message-ID: <007501bfa5a8$7e58c9a0$8dfee0d1@westbend.net> References: <l03020912b512b9e3bb4d@[153.9.17.27]> <l03020909b51c02a906cc@[153.9.17.27]>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "James B. Wilkinson" <jimmy@CS.cofc.EDU> > >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? > There are three ways to include/exclude a file from a PLIST. 1. Using a grep command to remove the entry from the PLIST (see www/apache13-fp) 2. Using an echo command to add a file to a PLIST (see mail/cyrus) 3. Use a different PLIST depending on if a variable is defined or a specific condition (i.e. PLIST, PLIST.notk) (see x11-clocks/emiclock). Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007501bfa5a8$7e58c9a0$8dfee0d1>