Date: Thu, 15 Sep 2016 18:53:19 +0300 From: abi <abi@abinet.ru> To: freebsd-ports@freebsd.org Subject: Re: What exactly are slave ports? Message-ID: <57DAC3EF.5040202@abinet.ru> In-Reply-To: <CAN6yY1uvee6rnfWuMqUhr91ciBeosv%2BDiunSgBXv_BbPtLiPSA@mail.gmail.com> References: <57D99EF0.5040202@abinet.ru> <CAN6yY1uvee6rnfWuMqUhr91ciBeosv%2BDiunSgBXv_BbPtLiPSA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I see. So, I'll create new one instead of slave. On 14.09.2016 22:20, Kevin Oberman wrote: > On Wed, Sep 14, 2016 at 12:03 PM, abi <abi@abinet.ru> wrote: > >> Hello, >> >> I want to add to existing port another one for the same program, but with >> different git branch and (possibly) with slightly different dependencies. >> Is this a good case for slave port ? >> Slave ports are not documented in porter handbook and I'm not sure how >> they work and when used. >> >> Thanks. >> > A slave port is a minor modification of the port to support different > functions. E.g. security/ssh-guard has slightly different builds, all from > a common source. One for each of the commonly used firewalls; ipfw, pf, > null. > > If the sources are different, a slave is not appropriate. Examples are the > various versions of postfix and clang. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57DAC3EF.5040202>