Second "RFC" on pkg-data idea for ports

Vivek Khera vivek at
Tue Apr 13 08:31:31 PDT 2004

On Apr 13, 2004, at 11:16 AM, Brian F. Feldman wrote:

> I'm not sure I understand why you don't just go all the way and embed 
> it in
> the Makefile.  Is it because make(1) is "slow"?  Since pkg/COMMENT 
> turned
> into pkg-comment and then COMMENT= in the Makefile, it's not hard to 
> imagine
> the same could be done for pkg/DESCR -> pkg-descr -> DESCR=, pkg/PLIST 
> ->
> pkg-plist -> PLIST=, and then every port would only be a single file.  
> Heck,
> even if Makefile became, itself, the XML PkgData file that defines
> everything in every port, it's not like there couldn't be a 
> portmake(1) that
> did "PkgData --Makefile" and called make(1) with all the rest of its
> arguments except doing a file descriptor redirection or temporary file
> redirection and adding a -f <contrived_Makefile>.

See  that's pretty much how it 
works, but their command is called "port" and the port description 
files are written in TCL.

Mostly, actually.  The patch files are still external.

More information about the freebsd-ports mailing list