From owner-freebsd-ports@FreeBSD.ORG  Mon Nov  8 15:15:46 2010
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0F4011065675;
	Mon,  8 Nov 2010 15:15:46 +0000 (UTC)
	(envelope-from lists@eitanadler.com)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com
	[209.85.160.182])
	by mx1.freebsd.org (Postfix) with ESMTP id 74FA28FC2D;
	Mon,  8 Nov 2010 15:15:45 +0000 (UTC)
Received: by gya6 with SMTP id 6so3545595gya.13
	for <multiple recipients>; Mon, 08 Nov 2010 07:15:44 -0800 (PST)
Received: by 10.42.223.132 with SMTP id ik4mr3284347icb.163.1289229344225;
	Mon, 08 Nov 2010 07:15:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.143.15 with HTTP; Mon, 8 Nov 2010 07:15:24 -0800 (PST)
In-Reply-To: <AANLkTim7AYUN+pNKQuY+C9yGLviRccjx7vc9hELmLymm@mail.gmail.com>
References: <AANLkTikV4nCaZeFH-OEq94LXHikibitcyv+VPnGH8TFt@mail.gmail.com>
	<4CD4602C.2080804@FreeBSD.org>
	<AANLkTi=9-tgiH2QH7wODncG8D9aw_z2guSUNQK_pajkF@mail.gmail.com>
	<AANLkTimJS+d-h6ub6Q_Ff7vX134exr-7s73o=+jY4af+@mail.gmail.com>
	<20101108084958.000042be@unknown>
	<AANLkTimzD0LjO+zCg1iPu2RzF7UF=pQkmMcHnMbx1jQd@mail.gmail.com>
	<AANLkTim7AYUN+pNKQuY+C9yGLviRccjx7vc9hELmLymm@mail.gmail.com>
From: Eitan Adler <lists@eitanadler.com>
Date: Mon, 8 Nov 2010 10:15:24 -0500
Message-ID: <AANLkTi=+AjohKAQAAu5_paBiO7mVcsFEnuzCwteKrCys@mail.gmail.com>
To: Baptiste Daroussin <bapt@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Cc: Bruce Cran <bruce@cran.org.uk>, freebsd ports <freebsd-ports@freebsd.org>,
	freebsd-sysinstall@freebsd.org, Randi Harper <randi@freebsd.org>,
	Garrett Cooper <gcooper@freebsd.org>
Subject: Re: Proposed OPTIONS replacement
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 15:15:46 -0000

If there is interest in writing a BSDL libdialog I would be interested
in working on such a project for the Google Summer of Code.
I'm cross posting to -ports and -sysinstall because this part of the
discussion started on -sysinstall.
Please keep future discussion on -ports as that is what the focus of
my proposal is.
...
> With libdialog it is not possible to mix radio button and "normal"
> button and for the options framework we need the be able to get the
> following feature imho:
>
> simple options: check box

My program has this

> exclusive options: radio button

My program has this

> exclusive options if a simple option is check (for example option X11
> allow to choose between the following options QT3 QT4 GTK etc)

My program does has this capability yet. I'm not exactly sure how to
indicate this on the command line. Perhaps some kind of
--requires-other option?

> group options: a user can check choose between 0-N options (check box)

> if a other options is activated example a port can be build with 2 or
> more gui toolkit at the same time: avidemux for example
> group options with at least one options checked (1-N).

My program does not yet have this capability. Perhaps a --min and a
--max option for radio options? This might be a pain to implement due
to the way my program handles radio options.  If there is a major need
for this feature I'll spend the time adding the feature.

> As far as I've looked into libdialog it is nearly impossible to handle
> in a simple (I may be wrong and missed some part of libdialog)

I don't know libdialog very well, but I know that with dialog(1) this
is impossible.

> Other choices will be :
> 1/ create a ncurses tool dedicated for the ports as Eitan began to do
> it (thanks for that :)) (this is my favorite choice)

I'm still looking for a comprehensive code review. I really want to
get my program as good as possible.


-- 
Eitan Adler