-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, 2 Feb 2015 16:54:37 -0800
Brian Dolbec wrote:
> > On 02.02.2015 22:58, Brian Dolbec wrote:
> > >
> > > sys-apps/portage-2.2.16 is ready for release and is just waiting
> > > for the news announcement about the new plug-in sync system being
> On Tue, 3 Feb 2015, Brian Dolbec wrote:
> New for git sync-type:
> sync-depth = n where n = {0,1,2,3,...} (optional, default = 1)
What do these values mean? You should either explain them, or don't
mention them at all. Especially, it is not obvious what the value 0
signifies (g
# Bernard Cafarelli (03 Feb 2015)
# Masked for removal in 30 days
# Requires GTK+2 audacious (<=3.2) with audclient (<=3.4)
# Bugs #411077 and #538464
x11-plugins/wmauda
--
Bernard Cafarelli (Voyageur)
Gentoo developer (NX, GNUstep, net-misc, llvm/clang, ...)
Dnia 2015-02-02, o godz. 15:06:40
Michał Górny napisał(a):
> Hi, everyone.
>
> Just after the news item got published, user Wes mailed me with
> a suggestion. While I think someone mentioned it earlier
> in the bikesheds over ffmpeg, I have completely forgotten about it
> and now I'd like to rec
On Mon, 2 Feb 2015 16:54:37 -0800 Brian Dolbec wrote:
> Attached is an updated news item.
[...]
> Changes: /etc/portage/repos.conf/*
> New for all repository types (needed):
> auto-sync = yes/no, true/false # default if absent: no/false
1. Why autosync is disabled by default? This b
On Tue, 3 Feb 2015 17:37:49 +0300 Andrew Savchenko wrote:
> On Mon, 2 Feb 2015 16:54:37 -0800 Brian Dolbec wrote:
> > Attached is an updated news item.
> [...]
>
> > Changes: /etc/portage/repos.conf/*
> > New for all repository types (needed):
> > auto-sync = yes/no, true/false # def
Dnia 2015-02-03, o godz. 01:22:27
Duncan <1i5t5.dun...@cox.net> napisał(a):
> > 2. There is some more work to get ebuilds correct (REQUIRED_USE).
> > However, this is a minor issue compared to the potential mistakes in
> > interpretation of USE='ffmpeg' and USE='libav'.
>
> ffmpeg-chooser.eclass
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/02/15 11:11 AM, Michał Górny wrote:
> Dnia 2015-02-03, o godz. 01:22:27 Duncan <1i5t5.dun...@cox.net>
> napisał(a):
>
>>> 2. There is some more work to get ebuilds correct
>>> (REQUIRED_USE). However, this is a minor issue compared to the
>>>
On Tue, 3 Feb 2015 17:37:49 +0300
Andrew Savchenko wrote:
> On Mon, 2 Feb 2015 16:54:37 -0800 Brian Dolbec wrote:
> > Attached is an updated news item.
> [...]
>
> > Changes: /etc/portage/repos.conf/*
> > New for all repository types (needed):
> > auto-sync = yes/no, true/false # d
On Tue, 3 Feb 2015 18:01:21 +0300
Andrew Savchenko wrote:
> On Tue, 3 Feb 2015 17:37:49 +0300 Andrew Savchenko wrote:
>
> 4. I don't fully understand how new plugin system is supposed to
> interact with layman.
>
> I far as I can see, the global goal is to replace layman by new
> sync system: i
If you want ffmpeg-ish features, at all, USE=ffmpeg.
If you'd like to use the libav implementation, USE=libav. If you'd prefer
to use the original ffmpeg implementation, USE=-libav.
This is simple. Why can't we just stick with this?
On Tue, 3 Feb 2015 08:36:54 -0800
Brian Dolbec wrote:
> > 1. Why autosync is disabled by default? This broke current
> > default for emerge --sync. And if users added overlays, they
> > most definitely want them to by synced by default as well.
> > So I propose to set auto-sync=yes by default.
Dnia 2015-02-03, o godz. 18:50:43
"Jason A. Donenfeld" napisał(a):
> If you want ffmpeg-ish features, at all, USE=ffmpeg.
>
> If you'd like to use the libav implementation, USE=libav. If you'd prefer
> to use the original ffmpeg implementation, USE=-libav.
>
>
> This is simple. Why can't we ju
On Tue, Feb 3, 2015 at 11:36 AM, Brian Dolbec wrote:
>
> You can't fix crap code to both keep the old crap handling while still
> giving you new decent handling for the same config.
>
I think that makes sense, and certainly many upstreams have made
changes this large.
However, it does make sense
On Tue, 3 Feb 2015 20:52:27 +0300
Diamond wrote:
> On Tue, 3 Feb 2015 08:36:54 -0800
> Brian Dolbec wrote:
>
> > > 1. Why autosync is disabled by default? This broke current
> > > default for emerge --sync. And if users added overlays, they
> > > most definitely want them to by synced by defaul
On 02/02/15 19:06, viv...@gmail.com wrote:
Il 02/02/2015 23:30, Pacho Ramos ha scritto:
El sáb, 31-01-2015 a las 16:48 -0500, Anthony G. Basile escribió:
Hi everyone,
We need to revert the following change to toolchain.eclass:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/too
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, 3 Feb 2015 13:25:39 -0500
Rich Freeman wrote:
> On Tue, Feb 3, 2015 at 11:36 AM, Brian Dolbec
> wrote:
> >
> > You can't fix crap code to both keep the old crap handling while
> > still giving you new decent handling for the same config.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/03/2015 02:04 PM, Michał Górny wrote:
> Dnia 2015-02-02, o godz. 15:06:40 Michał Górny
> napisał(a):
>
>> Hi, everyone.
>>
>> Just after the news item got published, user Wes mailed me with a
>> suggestion. While I think someone mentioned it
Markos Chandras wrote:
> we bloat the make.conf file with new variables every now and then
Although it often makes sense to set USE_EXPAND-variables
in make.conf, it is not *necessary* to do it in this way
and in this file:
It can also happen in USE or in /etc/portage/package.use
In fact, this i
On 02/03/2015 04:18 PM, Martin Vaeth wrote:
> Markos Chandras wrote:
>> we bloat the make.conf file with new variables every now and then
>
> Although it often makes sense to set USE_EXPAND-variables
> in make.conf, it is not *necessary* to do it in this way
> and in this file:
> It can also happ
20 matches
Mail list logo
