On Fri, 23 Jan 2015 16:45:34 -0600
Ben Kohler wrote:
>
> I think this should be in an ebuild. You mentioned that it's only
> needed ONCE, but it's needed ONCE for everytime one install gentoos,
> along the same lines as mirrorselect. A couple of years from now, do
> we want users to have to di
Michał Górny posted on Fri, 23 Jan 2015 20:13:34 +0100 as excerpted:
> Dnia 2015-01-21, o godz. 00:18:50 Duncan <1i5t5.dun...@cox.net>
> napisał(a):
>
>> Michał Górny posted on Tue, 20 Jan 2015 10:40:17 +0100 [as snipped]
>>
>> So based on this preliminary news item, I decided to get ahead of th
Hi,
Attaching the news item for planned USE=libav introduction.
The emphasis on letting users know that they may need to set USE=-libav
to get their systems back in working condition.
I hope that we've finally agreed on going for variant 1. I was trying
to come up with a hybrid possibly-friendly
Dnia 2015-01-20, o godz. 10:40:17
Michał Górny napisał(a):
> Dnia 2015-01-18, o godz. 21:44:05
> Michał Górny napisał(a):
>
> > Hello,
> >
> > I would like to commit the following flags as cpu_flags_x86_desc.
> > The list combines global USE flags with some local USE flags I've been
> > able t
Dnia 2015-01-24, o godz. 02:29:26
Andrew Savchenko napisał(a):
> On Sat, 24 Jan 2015 00:12:15 +0100 Michał Górny wrote:
> > To help you enable the correct USE flags, we are providing a Python
> > script tool generates the correct value using your /proc/cpuinfo.
> > It can be found in app-portage/
On Sat, 24 Jan 2015 00:12:15 +0100 Michał Górny wrote:
> To help you enable the correct USE flags, we are providing a Python
> script tool generates the correct value using your /proc/cpuinfo.
> It can be found in app-portage/cpuinfo2cpuflags package:
>
> $ emerge -1v app-portage/cpuinfo2cpuflag
On 01/23/2015 06:12 PM, Michał Górny wrote:
> To help you enable the correct USE flags, we are providing a Python
> script tool generates the correct value using your /proc/cpuinfo.
> It can be found in app-portage/cpuinfo2cpuflags package:
I think you accidentally a word here, but otherwise it lo
Dnia 2015-01-23, o godz. 17:56:49
Michael Orlitzky napisał(a):
> On 01/23/2015 05:38 PM, Michał Górny wrote:
> >
> > 3. Put it in an ebuild, after all. This will add a lot of complexity
> > but GPG comes for free, plus some people will actually test
> > and stabilize it.
> >
>
> I do. It seems
On 01/23/2015 05:38 PM, Michał Górny wrote:
>
> 3. Put it in an ebuild, after all. This will add a lot of complexity
> but GPG comes for free, plus some people will actually test
> and stabilize it.
>
I do. It seems like a lot of work, but we can test and quick-stable it.
Thank you.
>> If what
On Fri, 23 Jan 2015 16:16:25 -0500
Michael Orlitzky wrote:
> On 01/23/2015 03:22 PM, Michał Górny wrote:
> > Dnia 2015-01-23, o godz. 14:26:48
> > Michael Orlitzky napisał(a):
> >
> >> On 01/23/2015 02:13 PM, Michał Górny wrote:
> >>> To help you enable the correct USE flags, we are providing a
On Fri, Jan 23, 2015 at 4:38 PM, Michał Górny wrote:
>
> 3. Put it in an ebuild, after all. This will add a lot of complexity
> but GPG comes for free, plus some people will actually test
> and stabilize it.
>
>
I think this should be in an ebuild. You mentioned that it's only needed
ONCE, but i
Dnia 2015-01-23, o godz. 17:27:16
Michael Orlitzky napisał(a):
> On 01/23/2015 05:07 PM, Michał Górny wrote:
> >
> >> Even `wget --no-check-certificate` would be a big improvement.
> >
> > ...because?
> >
>
> You rule out some 13-year-olds in coffee shops as attackers. I
> overstated -- since
On Fri, Jan 23, 2015 at 3:18 PM, hasufell wrote:
>
> The problem I see now is that people will have a hard time to actually
> switch, because unlike gnutls we cannot have openssl and libressl be
> installed at the same time.
>
I personally find it annoying when people fork projects, decide not to
On 01/23/2015 05:07 PM, Michał Górny wrote:
>
>> Even `wget --no-check-certificate` would be a big improvement.
>
> ...because?
>
You rule out some 13-year-olds in coffee shops as attackers. I
overstated -- since the user isn't replying with any data, it's not a
big improvement, but it's still
Dnia 2015-01-24, o godz. 00:59:24
Andrew Savchenko napisał(a):
> On Fri, 23 Jan 2015 21:22:31 +0100 Michał Górny wrote:
> > > > To help you enable the correct USE flags, we are providing a Python
> > > > script which generates the correct value from your /proc/cpuinfo [1].
> > > > The Python scri
On Wed, 21 Jan 2015 01:13:08 + (UTC) Duncan wrote:
> Andrew Savchenko posted on Tue, 20 Jan 2015 23:59:23 +0300 as excerpted:
>
> > On Tue, 20 Jan 2015 12:17:35 -0800 Christopher Head wrote:
> >> On January 20, 2015 12:47:03 AM PST, Alexis Ballier
> >> wrote:
> >> >So, you're telling me that
Dnia 2015-01-23, o godz. 16:16:25
Michael Orlitzky napisał(a):
> On 01/23/2015 03:22 PM, Michał Górny wrote:
> > Dnia 2015-01-23, o godz. 14:26:48
> > Michael Orlitzky napisał(a):
> >
> >> On 01/23/2015 02:13 PM, Michał Górny wrote:
> >>> To help you enable the correct USE flags, we are providi
On Fri, 23 Jan 2015 21:22:31 +0100 Michał Górny wrote:
> > > To help you enable the correct USE flags, we are providing a Python
> > > script which generates the correct value from your /proc/cpuinfo [1].
> > > The Python script can be downloaded and executed using the following
> > > command:
> >
On Fri, Jan 23, 2015 at 3:16 PM, Michael Orlitzky wrote:
> On 01/23/2015 03:22 PM, Michał Górny wrote:
> > Dnia 2015-01-23, o godz. 14:26:48
> > Michael Orlitzky napisał(a):
> >
> >> On 01/23/2015 02:13 PM, Michał Górny wrote:
> >>> To help you enable the correct USE flags, we are providing a Py
On 01/23/2015 03:22 PM, Michał Górny wrote:
>
>> But that's not the biggest problem with the wget thing: the first time
>> someone runs this it's going to fail.
>>
>> $ wget -O - dev.gentoo.org/~mgorny/cpuinfo2cpuflags-x86.py | python
>> ...
>> Unable to determine PORTDIR, please set it befo
On 01/23/2015 03:22 PM, Michał Górny wrote:
> Dnia 2015-01-23, o godz. 14:26:48
> Michael Orlitzky napisał(a):
>
>> On 01/23/2015 02:13 PM, Michał Górny wrote:
>>> To help you enable the correct USE flags, we are providing a Python
>>> script which generates the correct value from your /proc/cpui
Dnia 2015-01-23, o godz. 14:26:48
Michael Orlitzky napisał(a):
> On 01/23/2015 02:13 PM, Michał Górny wrote:
> > To help you enable the correct USE flags, we are providing a Python
> > script which generates the correct value from your /proc/cpuinfo [1].
> > The Python script can be downloaded an
Anthony G. Basile:
> On 01/23/15 00:56, Michał Górny wrote:
>> Dnia 2015-01-23, o godz. 01:51:24
>> hasufell napisał(a):
>>
>>> Regarding the last libav discussion I think we should also go with a
>>> "libressl" USE flag instead of creating a virtual that makes handling
>>> SUBSLOTs impossible.
>>
On 01/23/2015 02:13 PM, Michał Górny wrote:
> To help you enable the correct USE flags, we are providing a Python
> script which generates the correct value from your /proc/cpuinfo [1].
> The Python script can be downloaded and executed using the following
> command:
>
> $ wget -O - dev.gentoo.o
Dnia 2015-01-21, o godz. 00:18:50
Duncan <1i5t5.dun...@cox.net> napisał(a):
> Michał Górny posted on Tue, 20 Jan 2015 10:40:17 +0100 as excerpted:
>
> > Display-If-Keyword: amd64 ~amd64 x86 ~x86
> >
> > The USE flags corresponding to intruction sets and other features
> > specific to the x86 arc
On 01/23/2015 01:48 AM, Alexis Ballier wrote:
> On Thu, 22 Jan 2015 09:06:39 -0800
> Zac Medico wrote:
>
> [...]
>>> That's what I understand from Michał's comment (quoting him):
>>>
1. if you have dynamic-deps enabled, portage will want to install
both ffmpeg (because of :=) and libav
On 01/23/15 00:56, Michał Górny wrote:
Dnia 2015-01-23, o godz. 01:51:24
hasufell napisał(a):
Regarding the last libav discussion I think we should also go with a
"libressl" USE flag instead of creating a virtual that makes handling
SUBSLOTs impossible.
If libressl and openssl would have matc
On Thu, 22 Jan 2015 09:06:39 -0800
Zac Medico wrote:
[...]
> > That's what I understand from Michał's comment (quoting him):
> >
> >> 1. if you have dynamic-deps enabled, portage will want to install
> >> both ffmpeg (because of :=) and libav (because of ||). The
> >> effective deps will look li
But they don't. See my two blog posts on the matter. ABI compatibility is
explicitly not. What they care about.
On 23 Jan 2015 05:56, "Michał Górny" wrote:
> Dnia 2015-01-23, o godz. 01:51:24
> hasufell napisał(a):
>
> > Regarding the last libav discussion I think we should also go with a
> > "l
29 matches
Mail list logo
