Date: Fri, 4 Aug 2006 19:56:23 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Jose Alonso Cardenas Marquez <acm@freebsd.org> Cc: cvs-ports@freebsd.org, garga@freebsd.org, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: cvs commit: ports/ftp Makefile ports/ftp/linux-curl Makefile distinfo.i386 Message-ID: <20060804195623.564c8a6e@Magellan.Leidinger.net> In-Reply-To: <200608041438.k74Ec3Wr096494@repoman.freebsd.org> References: <200608041438.k74Ec3Wr096494@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Jose Alonso Cardenas Marquez <acm@freebsd.org> (Fri, 4 Aug 2006 14:38:03 +0000 (UTC)): > acm 2006-08-04 14:38:03 UTC > > FreeBSD ports repository > > Modified files: > ftp Makefile > Added files: > ftp/linux-curl Makefile distinfo.i386 > Log: > - New port: ftp/linux-curl Please have a look at the handbook (as told in the description of AUTOMATIC_PLIST in bsd.linux-rpm.mk). There you can find some words about using static plists instead of plists which are generated at build time. The linux infrastructure ports are definitively cases where we can provide a static plist. Because of this I can't determine if this port contains just the lib or other stuff too. A way to just install the lib in case it is needed as a dependency would be nice, in case there's no reason to install the curl binary. Currently I can't come up with a reason why we need the curl binary, is there one I don't think of? In case there is a reason for the curl binary: the port is missing some BRANDELF_* stuff. Feel free to ask on emulation@ for review of linux ports. Bye, Alexander. -- Was my SOY LOAF left out in th'RAIN? It tastes REAL GOOD!! http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060804195623.564c8a6e>