Date: Fri, 25 Jun 2004 11:20:26 +0200 From: Marius Strobl <marius@alchemy.franken.de> To: FUJISHIMA Satsuki <sf@FreeBSD.org> Cc: Mario Sergio Fujikawa Ferreira <lioux@FreeBSD.org> Subject: Re: RFC: updating devel/libgnugetopt Message-ID: <20040625112026.A16432@newtrinity.zeist.de> In-Reply-To: <86y8mcsgin.wl%sf@FreeBSD.org>; from sf@FreeBSD.org on Fri, Jun 25, 2004 at 08:06:08AM %2B0900 References: <20040624142332.89957.qmail@exxodus.fedaykin.here> <20040624210835.A9582@newtrinity.zeist.de> <86y8mcsgin.wl%sf@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 25, 2004 at 08:06:08AM +0900, FUJISHIMA Satsuki wrote: > Once 5.3-RELEASE released, we have complete getopt_long_only() for 5.x > and libgnugetopt for 4.x. Do we really need to support 5.0R-5.2.1R? > Since existing 5.x RELEASE is for early adopter, I think marking them, > that ports depend directly on devel/libgnugetopt, BROKEN for > 500000 < OSVERSION < 502104 is enough. > > BROKEN= update your OS, it is outdated. > Well, I'd like to see this mess cleaned up as good as possible before 5.3 and marking such ports BROKEN on 500000 < OSVERSION < 502104 would mean also no support for 5.2.1. > At Thu, 24 Jun 2004 21:08:35 +0200, > Marius Strobl wrote: > > Btw., since __FreeBSD_version 502104 the libgnugetopt port is no > > longer required (as getopt_long_only() was added to the FreeBSD > > libc, too). So bsd.port.mk should grow an USE_GETOPT_LONG_ONLY > > (similar to the existing USE_GETOPT_LONG) and devel/libgnugetopt > > marked IGNORE accordingly afterwards (this involves fixing the > > handful of ports that directly depend on devel/libgnugetopt). > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040625112026.A16432>