On 06/18/2014 01:08, Alexandre Rostovtsev wrote:
> eix --depend -z virtual/pkgconfig -a --use -z abi_x86_32 -a --use -z
> abi_x86_64 --only-names | wc -l
Interesting, I got 294 (probably from my local dev tree). Close enough, thanks!
So, taking this count-packages script here:
http://dev.gent
On Tue, 2014-06-17 at 11:20 -0400, Joshua Kinard wrote:
> On 06/17/2014 10:56, Alexandre Rostovtsev wrote:
> > On Tue, 2014-06-17 at 10:17 -0400, Joshua Kinard wrote:
> >> What I'd like to see is a list of all affected packages so we all can get a
> >> sense of just how big the actual problem reall
On Tue, 17 Jun 2014 10:17:26 -0400
Joshua Kinard wrote:
> I'm a member of toolchain, but that's mostly historical because I used to
> play with a lot of the cross-compile stuff for MIPS and Sparc. Mike and
> Ryan are the two primaries in toolchain right now. If they don't see a
> problem with c
Joshua Kinard:
> Provide a technical counter-argument to that or propose a solution that
> people can agree on and you're going to find people are a LOT more willing
> to stand with you on fixing the perceived problem.
>
I start to think here is some confusion going on. We already proposed
soluti
On 06/17/2014 10:56, Alexandre Rostovtsev wrote:
> On Tue, 2014-06-17 at 10:17 -0400, Joshua Kinard wrote:
>> What I'd like to see is a list of all affected packages so we all can get a
>> sense of just how big the actual problem really is. All I am hearing so far
>> are unsubstantiated claims of
Joshua Kinard:
>> I have proposed numerous ways to communicate this problem to the user
>> without touching any of the precious toolchain/embedded packages. If no
>> one responds there, I'll just pick one and apply it.
>
> And what I am trying to tell you is that making hardmask threats don't solv
Dnia 2014-06-17, o godz. 10:56:41
Alexandre Rostovtsev napisał(a):
> On Tue, 2014-06-17 at 10:17 -0400, Joshua Kinard wrote:
> > What I'd like to see is a list of all affected packages so we all can get a
> > sense of just how big the actual problem really is. All I am hearing so far
> > are uns
On 06/17/2014 10:38, hasufell wrote:
> Joshua Kinard:
>>
>> "upstream" didn't say anywhere in that bug that they weren't interested.
>> They countered your reasoning with a technical argument. QA even states
>> that you need to file separate bugs for the various build failures. You
>> could set u
On Tue, 2014-06-17 at 10:17 -0400, Joshua Kinard wrote:
> What I'd like to see is a list of all affected packages so we all can get a
> sense of just how big the actual problem really is. All I am hearing so far
> are unsubstantiated claims of tree-wide breakage. Knowing which packages
> are brok
Joshua Kinard:
>
> "upstream" didn't say anywhere in that bug that they weren't interested.
> They countered your reasoning with a technical argument. QA even states
> that you need to file separate bugs for the various build failures. You
> could set up a master TRACKER bug for these crossdev-r
On 06/17/2014 10:22, Michał Górny wrote:
> Dnia 2014-06-17, o godz. 09:25:32
> Ian Stakenvicius napisał(a):
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> On 16/06/14 07:38 PM, Joshua Kinard wrote:
>>> Can $PATH be configured via our existing eselect tool to
>>> enable/disable the
On 06/17/2014 08:48, hasufell wrote:
> Joshua Kinard:
>>
>> Equally using the Council as a hammer all the time doesn't work in the
>> long-term, either.
>
> This is exactly the case where the council has to step in to solve
> global issues and those between projects (here it is embedded gentoo
>
Dnia 2014-06-17, o godz. 09:25:32
Ian Stakenvicius napisał(a):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 16/06/14 07:38 PM, Joshua Kinard wrote:
> > Can $PATH be configured via our existing eselect tool to
> > enable/disable the crossdev paths when needed?
> >
>
> Technically
On 06/17/2014 08:49, Rich Freeman wrote:
>
> Is there a list/etc for crossdev? I'd think that the users and
> maintainers of crossdev collectively have the biggest vested interest
> in addressing these issues. They're also the ones who can vouch for
> how big of a problem this is.
toolchain is
On 06/17/2014 08:30, hasufell wrote:
> Joshua Kinard:
>> On 06/16/2014 21:47, hasufell wrote:
>>> Joshua Kinard:
How big of a patch would this change require to the existing crossdev
ebuild?
>>>
>>> Probably quite trivial, but since vapier said "bs" to that proposal
>>> (transl
Rich Freeman:
> On Tue, Jun 17, 2014 at 8:30 AM, hasufell wrote:
>> No, that's not how opensource works. You don't work on things after
>> "upstream" said "not interested".
>
> That is hardly true though - which is why we have 47 different
> implementations of everything to debate the merits of.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/06/14 07:38 PM, Joshua Kinard wrote:
> Can $PATH be configured via our existing eselect tool to
> enable/disable the crossdev paths when needed?
>
Technically it could but not really ; PATH is an environment thing,
AFAIK all eselect could do
On Tue, Jun 17, 2014 at 8:30 AM, hasufell wrote:
> No, that's not how opensource works. You don't work on things after
> "upstream" said "not interested".
That is hardly true though - which is why we have 47 different
implementations of everything to debate the merits of. :)
Besides, if this we
Joshua Kinard:
>
> Equally using the Council as a hammer all the time doesn't work in the
> long-term, either.
This is exactly the case where the council has to step in to solve
global issues and those between projects (here it is embedded gentoo
project and multilib project).
Joshua Kinard:
> On 06/16/2014 21:47, hasufell wrote:
>> Joshua Kinard:
>>>
>>> How big of a patch would this change require to the existing crossdev
>>> ebuild?
>>>
>>
>> Probably quite trivial, but since vapier said "bs" to that proposal
>> (translates to "bullshit" I guess) I'll not put any wor
Ryan Hill:
> If doing something dumb like installing a i686 crossdev toolchain on
> x86_64 breaks things, it's because you've done something dumb. Stop doing
> that and things should work better.
>
There have been several reasons mentioned to do what you call dumb. I'm
not going to repeat them.
21 matches
Mail list logo
