On czw, 2017-06-01 at 23:31 +0200, Michał Górny wrote:
> On czw, 2017-06-01 at 10:55 +0200, Alexis Ballier wrote:
> > On Wed, 31 May 2017 21:02:24 +0200
> > Michał Górny wrote:
> >
> > > On śro, 2017-05-31 at 19:39 +0200, Alexis Ballier wrote:
> > > > > > Again, you *need* to process the constra
>> A space separated list of the corresponding debian packages should be
>> written in the field
>>
> Why space separated?
> Its already legal to specify the field multiple times, and it should
> work better that way for consistency with things that can already parse
> XML.
>
> That way there's
On czw, 2017-06-01 at 20:17 -0500, A. Wilcox wrote:
> unpopular, unwanted opinion:
>
> just have users of a *source based distro* where the emphasis is
> *choice* actually choose what they want?
>
> What is the big deal with the way REQUIRED_USE works now? "Users have
> to do something". You al
On pią, 2017-06-02 at 04:56 +0700, Vadim A. Misbakh-Soloviov wrote:
> 1) Dear Vim Team, can we hear your opinions?
>
> 2) I'd like to know if discussion participants really differs my eselect-php-
> like suggestion (where all scripts goes to another directory, controlled by
> neither of vims, and
On 06/01/2017 06:09 PM, Kent Fredric wrote:
> On Thu, 1 Jun 2017 23:18:22 +0200
> Jonas Stein wrote:
>
>> A space separated list of the corresponding debian packages should be
>> written in the field
>>
>
> Why space separated?
>
> Its already legal to specify the field multiple times, and it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/06/17 20:28, Rich Freeman wrote:
> On Thu, Jun 1, 2017 at 9:17 PM, A. Wilcox
> wrote:
>>
>> just have users of a *source based distro* where the emphasis is
>> *choice* actually choose what they want?
>>
>> What is the big deal with the way
On Thu, Jun 1, 2017 at 9:17 PM, A. Wilcox wrote:
>
> just have users of a *source based distro* where the emphasis is
> *choice* actually choose what they want?
>
> What is the big deal with the way REQUIRED_USE works now? "Users have
> to do something".
The issue is that there isn't any value b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
unpopular, unwanted opinion:
just have users of a *source based distro* where the emphasis is
*choice* actually choose what they want?
What is the big deal with the way REQUIRED_USE works now? "Users have
to do something". You always have to do s
On Thu, 1 Jun 2017 09:38:01 -0400
"Walter Dnes" wrote:
> As mentioned elsewhere, what happens when two or three other people
> do their own forks? Plugin 1 works with vim A and B but not C or D.
> Plugin 2 works with vim A and C and D but not B. The number of
> directories could potentially b
On Thu, 1 Jun 2017 23:18:22 +0200
Jonas Stein wrote:
> A space separated list of the corresponding debian packages should be
> written in the field
>
Why space separated?
Its already legal to specify the field multiple times, and it should
work better that way for consistency with things that
1) Dear Vim Team, can we hear your opinions?
2) I'd like to know if discussion participants really differs my eselect-php-
like suggestion (where all scripts goes to another directory, controlled by
neither of vims, and then users should/can manually dis-/enable modules for
each of vim they want
On czw, 2017-06-01 at 10:55 +0200, Alexis Ballier wrote:
> On Wed, 31 May 2017 21:02:24 +0200
> Michał Górny wrote:
>
> > On śro, 2017-05-31 at 19:39 +0200, Alexis Ballier wrote:
> > > > > Again, you *need* to process the constraints in order. '!a?
> > > > > ( b ) !b? ( a )' is not deterministic
Hello,
this RFC is about the addition of a new field
to metadata.xml
The field should contain a list of the equivalent debian package names,
or a defined string for NONE or UNSET.
A feature request ticket was prepared here:
https://bugs.gentoo.org/show_bug.cgi?id=619132
1. Motivation
=
This will come in handy for users who enable LTO, since they need to use
the gcc wrappers for 'ar', 'nm', and 'ranlib'.
The default program search order becomes:
${CHOST}-gcc-ar
${CHOST}-ar
gcc-ar
ar
This matches the behavior of a typical autoconf call:
AC_CHECK_TOOLS(AR, [gcc-ar ar])
---
ecla
---
eclass/toolchain-funcs.eclass | 39 +++
1 file changed, 31 insertions(+), 8 deletions(-)
diff --git a/eclass/toolchain-funcs.eclass b/eclass/toolchain-funcs.eclass
index a0c359a950b2..b402a9ff2780 100644
--- a/eclass/toolchain-funcs.eclass
+++ b/eclass/tool
On Thu, 1 Jun 2017 09:38:01 -0400
"Walter Dnes" wrote:
> On Wed, May 31, 2017 at 11:54:59PM +0100, Ciaran McCreesh wrote
> > - Have a separate anyvimishthing directory, and make both vim and
> > neovim look there, and only make plugins that have been tested to
> > work with both install to that di
On Wed, May 31, 2017 at 11:54:59PM +0100, Ciaran McCreesh wrote
> - Have a separate anyvimishthing directory, and make both vim and
> neovim look there, and only make plugins that have been tested to work
> with both install to that directory.
As mentioned elsewhere, what happens when two or th
On Wed, 31 May 2017 21:02:24 +0200
Michał Górny wrote:
> On śro, 2017-05-31 at 19:39 +0200, Alexis Ballier wrote:
> > > > Again, you *need* to process the constraints in order. '!a?
> > > > ( b ) !b? ( a )' is not deterministic when none of a and b are
> > > > enabled otherwise.
> > >
> > >
> - Have a separate anyvimishthing directory, and make both vim and
> neovim look there, and only make plugins that have been tested to work
> with both install to that directory.
Actually it is almost the thing I described as "second" eselect variant.
Although, you suggest for gentoo devs to chec
19 matches
Mail list logo
