Hi.
We have LINGUAS support in portage for quite some time now, but how do
we handle LINGUAS? It's not as evident as it seems and thus we need some
guidelines. So I'll formulate few questions below but first let's look
how portage works with LINGUAS. If you know this skip to Questions
section belo
On 6/4/10 5:11 PM, "Paweł Hajdan, Jr." wrote:
> What do you think about doing the following change in
> /usr/portage/profiles/targets/developer/make.defaults:
The following change has now landed in CVS:
Index: targets/developer/make.defaults
===
On Wed, Jun 09, 2010 at 11:38:03AM +0400, Peter Volkov wrote:
> 1. Do we want all packages to support LINGUAS if possible? It is
> possible to leave gettext based package without LINGUAS and everything
> will just work, but I think that it's good idea to make supported
> languages visible to user t
On Tue, 8 Jun 2010 21:59:11 +0200
José María Alonso wrote:
> On Tue, Jun 08, 2010 at 06:25:17PM +0200, Jeroen Roovers wrote:
> > On Tue, 8 Jun 2010 13:14:07 +0200
> > José María Alonso wrote:
> >
> > > I would be very pleased to maintain this package:
> > >
> > > > app-doc/repodoc
> >
> > >
Mike Frysinger wrote:
> people want it and i havent seen any compelling reason to avoid it
> anymore, so let's rock
For the record: It is now rocked.
--
Jim Ramsay
Gentoo Developer (rox/fluxbox/gkrellm/vim)
signature.asc
Description: PGP signature
Harald van Dijk posted on Wed, 09 Jun 2010 21:21:44 +0200 as excerpted:
> Firstly, don't use == with test. It's not portable. The bash built-in
> test supports ==. Other test implementations don't, such as the one from
> GNU coreutils, and the built-in test in other shells, don't. If you use
> test
