Date: Sun, 14 Jan 2007 00:39:06 +0300 From: "Andrew Pantyukhin" <infofarmer@FreeBSD.org> To: "Robert Huff" <roberthuff@rcn.com> Cc: FreeBSD Ports <ports@freebsd.org> Subject: Re: Restricting (human) language and character set in /usr/ports Message-ID: <cb5206420701131339s66f2b3f9s2924a55c429ef501@mail.gmail.com> In-Reply-To: <17833.15710.478810.6251@jerusalem.litteratus.org> References: <cb5206420701131101l21807993ld15c899e6754ec02@mail.gmail.com> <17833.15710.478810.6251@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/13/07, Robert Huff <roberthuff@rcn.com> wrote: > > Andrew Pantyukhin writes: > > > I'm not sure if there's a policy already, but it seems > > we have discussed this before. > > > > Can we limit /usr/ports (the whole ports collection) to > > English language and ASCII characters? This restriction > > should probably apply to all text data (with possible > > exception for patches). > > I don't follow this issue (much), so could you explain what's > broken about the /status quo/? It depends on what you mean by /status quo/, but in short, when I look at COMMENT, pkg-descr, pkg-message, comments in Makefile and other such text data, I expect to see English language and ASCII characters. There are ports that don't follow this expectation and I'd like to change that.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420701131339s66f2b3f9s2924a55c429ef501>