Date: Tue, 12 Apr 2005 11:22:28 -0500 From: Scot Hetzel <swhetzel@gmail.com> To: Alejandro Pulver <alejandro@varnet.biz> Cc: Florent Thoumie <flz@xbsd.org> Subject: Re: Creating port with options Message-ID: <790a9fff0504120922217ad444@mail.gmail.com> In-Reply-To: <20050411203859.33d6c45f@ale.varnet.bsd> References: <20050411175526.54ffd260@ale.varnet.bsd> <20050411211923.GA9149@xor.obsecurity.org> <20050411184818.494ac35e@ale.varnet.bsd> <20050412005541.58ea5f0c@it.buh.cameradicommercio.ro> <1113260537.89967.48.camel@cream.xbsd.org> <20050411203859.33d6c45f@ale.varnet.bsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 11, 2005 6:38 PM, Alejandro Pulver <alejandro@varnet.biz> wrote: > Wich is the best way to manage conflictive options inside the OPTIONS > variable? > That should be work, but it may store the bad option in the options file. They'll just have to do a make reconfig to correct it. If you could split the port into 3 seperate ports: *-server *-x11-client *-ncurses-client Then you wouldn't need to worry about using the OPTIONS variable. This way you could make the *-client ports depend on the *-server port. Scot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0504120922217ad444>