Rich Freeman posted on Mon, 26 Jan 2015 09:20:30 -0500 as excerpted:
> Honestly, I think we should really reconsider the current GLSA policy.
What's the next step, not to step on anyone's toes? It's going to take
coordination, so get a sense of the council first and then see what the
security
On 01/26/2015 01:08 PM, Rich Freeman wrote:
> On Mon, Jan 26, 2015 at 5:43 AM, Peter Stuge wrote:
>> Rich Freeman wrote:
>>> I personally find it annoying when people fork projects, decide not to
>>> maintain ABI compatibility with the original project, and then keep
>>> filenames the same/etc suc
On Mon, Jan 26, 2015 at 6:18 AM, Rich Freeman wrote:
> On Mon, Jan 26, 2015 at 7:00 AM, Alexis Ballier
> wrote:
> > On Mon, 26 Jan 2015 12:37:09 +0100
> > Alexis Ballier wrote:
> >
> >> > media-video/mplayer2 or media-video/mpv may be used as a more
> >> > modern replacement.
> >>
> >> Don't re
On Sat, 24 Jan 2015 12:03:27 +0100 Michał Górny wrote:
> Dnia 2015-01-21, o godz. 11:05:34
> Michał Górny napisał(a):
>
> > Parent namespace solution
> > -
> >
> > The alternative is to wrap distcc so that parent network namespace is
> > regained. Sadly, for a start this
Hi,
On Sun, 25 Jan 2015 14:59:01 +0100 Michał Górny wrote:
> Dnia 2015-01-21, o godz. 11:05:34
> Michał Górny napisał(a):
>
> > Generic proxy solution
> > --
> >
> > The simplest solution so far seems to be setting a generic SOCKS proxy
> > inside the build environment, and
Dnia 2015-01-26, o godz. 23:11:35
"viv...@gmail.com" napisał(a):
> Il 24/01/2015 00:12, Michał Górny ha scritto:
> > $ emerge -1v app-portage/cpuinfo2cpuflags
> > $ cpuinfo2cpuflags-x86.py
> it's
>
> cpuinfo2cpuflags-x86
>
> w/o the .py here
floppym already told me, I updated it locally bu
Il 24/01/2015 00:12, Michał Górny ha scritto:
> $ emerge -1v app-portage/cpuinfo2cpuflags
> $ cpuinfo2cpuflags-x86.py
it's
cpuinfo2cpuflags-x86
w/o the .py here
On Mon, 26 Jan 2015 09:20:30 -0500
Rich Freeman wrote:
> On Mon, Jan 26, 2015 at 8:21 AM, Duncan <1i5t5.dun...@cox.net> wrote:
> > The result of the current policy is that if you're waiting for the
> > GLSA, unless it's _extreme_ priority (heartbleed level), on at
> > least amd64, you're very oft
On 01/26/2015 03:57 AM, Alexis Ballier wrote:
> On Fri, 23 Jan 2015 09:19:19 -0800
> Zac Medico wrote:
>
>>> what Michał claims is that 'foo' will want ffmpeg, no matter what.
>>
>> Maybe he's talking about some case where portage failed to trigger a
>> rebuild when appropriate. We've had a numbe
# Johannes Huber (26 Jan 2015)
# Masked for removal in 30 days, bug #537746.
# Superseded by kde-base/kdebase-kioslaves ages ago.
kde-misc/kio-ftps
--
Johannes Huber (johu)
Gentoo Linux Developer / KDE Team
GPG Key ID F3CFD2BD
signature.asc
Description: This is a digitally signed message part.
Dnia 2015-01-26, o godz. 07:18:13
Rich Freeman napisał(a):
> On Mon, Jan 26, 2015 at 7:00 AM, Alexis Ballier wrote:
> > On Mon, 26 Jan 2015 12:37:09 +0100
> > Alexis Ballier wrote:
> >
> >> > media-video/mplayer2 or media-video/mpv may be used as a more
> >> > modern replacement.
> >>
> >> Don'
Dnia 2015-01-26, o godz. 16:40:35
Alexis Ballier napisał(a):
> On Mon, 26 Jan 2015 16:20:10 +0100
> Michał Górny wrote:
>
> > Dnia 2015-01-26, o godz. 12:41:00
> > Alexis Ballier napisał(a):
> >
> > > On Sat, 24 Jan 2015 00:35:39 +0100
> > > Michał Górny wrote:
> > >
> > > > Title: CPU_FLAG
Dnia 2015-01-26, o godz. 12:41:00
Alexis Ballier napisał(a):
> On Sat, 24 Jan 2015 00:35:39 +0100
> Michał Górny wrote:
>
> > Title: CPU_FLAGS_X86 introduction
> > Author: Michał Górny
> > Content-Type: text/plain
> > Posted: 2015-01-xx
> > Revision: 1
> > News-Item-Format: 1.0
> > Display-If-
On Jan 26, 2015 11:01 AM, "Peter Stuge" wrote:
>
> Rich Freeman wrote:
>
>
> > there wouldn't be an /etc/init.d, but rather a bazillion
> > /pkg/guid/etc/init.d directories or something like that
>
> I guess an abstraction akin to pkg-config could solve the problem.
>
Sort of. You can't call a se
Rich Freeman wrote:
> >> I personally find it annoying when people fork projects, decide not to
> >> maintain ABI compatibility with the original project, and then keep
> >> filenames the same/etc such that the packages collide in their
> >> recommended configurations.
> >
> > Some people do it on
On Mon, Jan 26, 2015 at 10:30 AM, Michał Górny wrote:
> Dnia 2015-01-26, o godz. 12:15:49
> Peter Stuge napisał(a):
>
>> "the ffmpeg fork" above is very confusing because libav is the ffmpeg
>> fork, and I think what you mean here is simply "ffmpeg". I suggest:
>
> Well, you aren't correct which
On Mon, 26 Jan 2015 16:20:10 +0100
Michał Górny wrote:
> Dnia 2015-01-26, o godz. 12:41:00
> Alexis Ballier napisał(a):
>
> > On Sat, 24 Jan 2015 00:35:39 +0100
> > Michał Górny wrote:
> >
> > > Title: CPU_FLAGS_X86 introduction
> > > Author: Michał Górny
> > > Content-Type: text/plain
> > >
Dnia 2015-01-26, o godz. 12:15:49
Peter Stuge napisał(a):
> Michał Górny wrote:
> > Title: USE=libav introduction
> > Author: Micha?? G??rny
>
> Your mailer doesn't set charset for the .txt attachment.
NeedPatch :).
> > Content-Type: text/plain
> > Posted: 2015-01-yy
> > Revision: 1
> > News-
Dnia 2015-01-26, o godz. 12:57:36
Alexis Ballier napisał(a):
> On Fri, 23 Jan 2015 09:19:19 -0800
> Zac Medico wrote:
>
> > > what Michał claims is that 'foo' will want ffmpeg, no matter what.
> >
> > Maybe he's talking about some case where portage failed to trigger a
> > rebuild when appropr
Dnia 2015-01-26, o godz. 12:41:00
Alexis Ballier napisał(a):
> On Sat, 24 Jan 2015 00:35:39 +0100
> Michał Górny wrote:
>
> > Title: CPU_FLAGS_X86 introduction
> > Author: Michał Górny
> > Content-Type: text/plain
> > Posted: 2015-01-xx
> > Revision: 1
> > News-Item-Format: 1.0
> > Display-If-
On Mon, Jan 26, 2015 at 8:21 AM, Duncan <1i5t5.dun...@cox.net> wrote:
> The result of the current policy is that if you're waiting for the GLSA,
> unless it's _extreme_ priority (heartbleed level), on at least amd64,
> you're very often sitting there exposed for well over a week, and too
> often a
Róbert Čerňanský posted on Sun, 25 Jan 2015 14:27:50 +0100 as excerpted:
> On Sun, 25 Jan 2015 04:29:43 + (UTC)
> Duncan <1i5t5.dun...@cox.net> wrote:
>> [...]
>
> More frequent updates is most likely the reason that you do not have to
> edit use flags every time.
With the information below,
On Mon, 26 Jan 2015 07:18:13 -0500
Rich Freeman wrote:
> On Mon, Jan 26, 2015 at 7:00 AM, Alexis Ballier
> wrote:
> > On Mon, 26 Jan 2015 12:37:09 +0100
> > Alexis Ballier wrote:
> >
> >> > media-video/mplayer2 or media-video/mpv may be used as a more
> >> > modern replacement.
> >>
> >> Don't
On Mon, Jan 26, 2015 at 7:00 AM, Alexis Ballier wrote:
> On Mon, 26 Jan 2015 12:37:09 +0100
> Alexis Ballier wrote:
>
>> > media-video/mplayer2 or media-video/mpv may be used as a more
>> > modern replacement.
>>
>> Don't recommend mplayer2, afaik it's dead.
>
> Also, I'd drop "modern" from there
On Mon, Jan 26, 2015 at 5:43 AM, Peter Stuge wrote:
> Rich Freeman wrote:
>> I personally find it annoying when people fork projects, decide not to
>> maintain ABI compatibility with the original project, and then keep
>> filenames the same/etc such that the packages collide in their
>> recommende
On Mon, 26 Jan 2015 12:37:09 +0100
Alexis Ballier wrote:
> > media-video/mplayer2 or media-video/mpv may be used as a more
> > modern replacement.
>
> Don't recommend mplayer2, afaik it's dead.
Also, I'd drop "modern" from there: I don't see much more modernity in
those forks except maybe young
On Fri, 23 Jan 2015 09:19:19 -0800
Zac Medico wrote:
> > what Michał claims is that 'foo' will want ffmpeg, no matter what.
>
> Maybe he's talking about some case where portage failed to trigger a
> rebuild when appropriate. We've had a number of bugs like this that
> have been fixed. The most r
On Sat, 24 Jan 2015 11:20:54 +0100
Michał Górny wrote:
> > Where is libav USE and package set as default over ffmpeg? I haven't
> > found that in profiles/ dir :/ (or is it going to be done when
> > implementing this?)
>
> Right now in virtual/ffmpeg.
not entirely true since the virtual won't t
On Sat, 24 Jan 2015 00:35:39 +0100
Michał Górny wrote:
> Title: CPU_FLAGS_X86 introduction
> Author: Michał Górny
> Content-Type: text/plain
> Posted: 2015-01-xx
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Keyword: amd64 ~amd64 x86 ~x86
but why ?
will you write another news item for
On Sat, 24 Jan 2015 00:39:04 +0100
Michał Górny wrote:
> Users who want to use the ffmpeg fork
> instead need to specify USE=-libav explicitly.
As Peter said, please avoid such controversial statements.
> The most notable example of such package is
> media-video/mplayer which relies on deprecat
Michał Górny wrote:
> Title: USE=libav introduction
> Author: Micha?? G??rny
Your mailer doesn't set charset for the .txt attachment.
> Content-Type: text/plain
> Posted: 2015-01-yy
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Installed: media-video/ffmpeg
> Display-If-Installed: media-vid
Rich Freeman wrote:
> I personally find it annoying when people fork projects, decide not to
> maintain ABI compatibility with the original project, and then keep
> filenames the same/etc such that the packages collide in their
> recommended configurations.
Some people do it on purpose, with the o
32 matches
Mail list logo
