Date: Tue, 12 Nov 2013 15:52:11 -0500 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: Big Lebowski <spankthespam@gmail.com> Cc: freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Best way to make the port install another port Message-ID: <44habhbax0.fsf@be-well.ilk.org> In-Reply-To: <CAHcXP%2Bc%2B9g85TJCqrQBoAPuH6tCL=b_WR_jAya%2BcFv-QYUXjyg@mail.gmail.com> (Big Lebowski's message of "Tue, 12 Nov 2013 18:58:45 %2B0000") References: <CAHcXP%2BeZZ3tYXFmUNJhqU%2B69rVhqw-%2Bae7FMZhfz=BZ8XjdqbQ@mail.gmail.com> <CAHcXP%2Bc%2B9g85TJCqrQBoAPuH6tCL=b_WR_jAya%2BcFv-QYUXjyg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Big Lebowski <spankthespam@gmail.com> writes: > On Sun, Nov 10, 2013 at 6:02 PM, Big Lebowski <spankthespam@gmail.com>wrote: > >> Hi, >> >> I wanted to add an option to one of my ports to optionally install >> commandline tool, that's in another port. Doing the options part is easy >> and clear, but how should I add that port to build procedure to do it the >> right-way? The most obvious way would be to add RUN_DEPENDS+=, but the >> original port doesnt really depend on this tools... >> >> Another question is to where is the best place to put such dependency? >> Post install, pre install? >> >> Thanks in advance! >> > > Just bumping it in a hope of someone actually knowing the answer... Yes, it's RUN_DEPENDS. See the OPTIONS example in the porter's handbook for a case.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44habhbax0.fsf>