hardened systems (as well as my non-hardened ones) have been running
FEATURES=sfperms for years with no known bugs. so unless someone has
a compelling reason otherwise, i'll be enabling this in
profiles/default/linux/ for all linux systems.
-mike
On 10/25/2010 03:37 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> I would like to suggest that setting Python 3.1 as main active version of
> Python be officially
> supported and recommended for Gentoo developers since 2010-12-01. Majority of
> packages supporting
> only Python 2.* have been p
Hi all,
Based on our participation in the Summer of Code, Google invited us to
apply for their revived program for 13-18 year olds called Google
Code-In [1-2]. The basic idea is that students will complete a series of
small tasks rather than one huge project, and the tasks don't even have
to b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25-10-2010 15:13, Arfrever Frehtes Taifersar Arahesis wrote:
> 2010-10-25 16:31:41 Petteri Räty napisał(a):
>> On 10/25/2010 02:54 PM, Arfrever Frehtes Taifersar Arahesis (arfrever)
>> wrote:
>>> arfrever10/10/25 11:54:19
>>>
>>> Modified:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25-10-2010 13:37, Arfrever Frehtes Taifersar Arahesis wrote:
> I would like to suggest that setting Python 3.1 as main active version of
> Python be officially
> supported and recommended for Gentoo developers since 2010-12-01. Majority of
> packa
On Monday 25 October 2010 19:06:45 Diego Elio Pettenò wrote:
> Il giorno lun, 25/10/2010 alle 18.50 -0300, Alexis Ballier ha scritto:
> > Am I missing something obvious or is it just hiding a bug in the
> > linux
> > headers? I see no usage of INT_MAX in the patched .c file...
>
> Upstream seem no
Il giorno lun, 25/10/2010 alle 18.50 -0300, Alexis Ballier ha scritto:
>
>
> Am I missing something obvious or is it just hiding a bug in the
> linux
> headers? I see no usage of INT_MAX in the patched .c file...
Upstream seem not to care about fixing that; we used to have a patch to
"fix" lin
On Monday 25 October 2010 06:06:15 Samuli Suominen (ssuominen) wrote:
> ssuominen10/10/25 09:06:15
>
> Added:mpfc-1.3.7-INT_MAX.patch
> Log:
> Missing include limits.h, required by recent linux-headers for cdrom.h
> and INT_MAX. Fix installation with recent coreutils wrt
On Mon, 25 Oct 2010 15:37:41 +0200
Arfrever Frehtes Taifersar Arahesis wrote:
> I would like to suggest that setting Python 3.1 as main active
> version of Python be officially supported and recommended for Gentoo
> developers since 2010-12-01. Majority of packages supporting only
> Python 2.* ha
On 10/25/2010 06:23 PM, Petteri Räty wrote:
> On 10/25/2010 04:24 PM, Arfrever Frehtes Taifersar Arahesis wrote:
>> I would like to request that 2 additional features are added to EAPI="4".
>> These features will be needed for further development of python.eclass.
>>
>> 1. Support for "." character
Il giorno lun, 25/10/2010 alle 19.23 +0300, Petteri Räty ha scritto:
>
> Ideally we should have consistency across languages so if we go down
> this road then for example ruby should eventually support it too. Ruby
> people: can you provide your input.
We don't really care since we use the Ruby
On 10/25/2010 04:24 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> I would like to request that 2 additional features are added to EAPI="4".
> These features will be needed for further development of python.eclass.
>
> 1. Support for "." characters in names of USE flags
Ideally we should have c
Am 25.10.2010 16:43, schrieb Fabio Erculiani:
> Implementing a feature to just satisfy your tiny, corner-case (how
> many people would take benefit out of it?) use case is just against
> any software engineering best practice, and it's a good path towards
> bloat and complexity. I think people can
Arfrever Frehtes Taifersar Arahesis said:
> 2010-10-25 16:31:41 Petteri Räty napisał(a):
> > On 10/25/2010 02:54 PM, Arfrever Frehtes Taifersar Arahesis (arfrever)
> > wrote:
> > > arfrever10/10/25 11:54:19
> > >
> > > Modified: python.eclass
> > > Log:
> > > Set IUSE in EAP
On 10/25/2010 06:13 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> 2010-10-25 16:31:41 Petteri Räty napisał(a):
>> On 10/25/2010 02:54 PM, Arfrever Frehtes Taifersar Arahesis (arfrever)
>> wrote:
>>> arfrever10/10/25 11:54:19
>>>
>>> Modified: python.eclass
>>> Log:
>>> Set
On Mon, 25 Oct 2010 17:13:00 +0200
Arfrever Frehtes Taifersar Arahesis wrote:
> The attached patch could be applied if EAPI="4" doesn't contain
> support for "." in IUSE. Should I apply this patch now?
You should stop guessing what will or will not be in EAPI 4 and just
not commit anything EAPI 4
2010-10-25 16:31:41 Petteri Räty napisał(a):
> On 10/25/2010 02:54 PM, Arfrever Frehtes Taifersar Arahesis (arfrever)
> wrote:
> > arfrever10/10/25 11:54:19
> >
> > Modified: python.eclass
> > Log:
> > Set IUSE in EAPI >=4.
> > Rename _parse_PYTHON_DEPEND() to _python_parse
Le lundi 25 octobre 2010 à 19:44 +0530, Nirbheek Chauhan a écrit :
> On Mon, Oct 25, 2010 at 7:07 PM, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > I would like to suggest that setting Python 3.1 as main active version of
> > Python be officially
> > supported and recommended for Gentoo develo
2010-10-25 16:37:38 Fabio Erculiani napisał(a):
> Please, just, no.
> Projects and people are just not ready, yet. And even Python experts
> at #python tell to stay away from Py3, last time I checked.
#python channel isn't maintained by Python upstream developers.
--
Arfrever Frehtes Taifersar A
2010-10-25 16:03:01 Ciaran McCreesh napisał(a):
> On Mon, 25 Oct 2010 15:56:18 +0200
> Arfrever Frehtes Taifersar Arahesis wrote:
> > 2010-10-25 15:42:00 Ciaran McCreesh napisał(a):
> > > On Mon, 25 Oct 2010 15:24:23 +0200
> > > Arfrever Frehtes Taifersar Arahesis wrote:
> > > > 1. Support for ".
2010-10-25 16:43:43 Fabio Erculiani napisał(a):
> Implementing a feature to just satisfy your tiny, corner-case (how
> many people would take benefit out of it?) use case is just against
> any software engineering best practice, and it's a good path towards
> bloat and complexity. I think people ca
Implementing a feature to just satisfy your tiny, corner-case (how
many people would take benefit out of it?) use case is just against
any software engineering best practice, and it's a good path towards
bloat and complexity. I think people can understand "python_abis_2_5"
well enough, besides bein
Please, just, no.
Projects and people are just not ready, yet. And even Python experts
at #python tell to stay away from Py3, last time I checked.
--
Fabio Erculiani
On 10/25/2010 02:54 PM, Arfrever Frehtes Taifersar Arahesis (arfrever)
wrote:
> arfrever10/10/25 11:54:19
>
> Modified: python.eclass
> Log:
> Set IUSE in EAPI >=4.
> Rename _parse_PYTHON_DEPEND() to _python_parse_PYTHON_DEPEND() and unset it
> after its using.
> Ban NEE
В Пнд, 25/10/2010 в 09:07 -0500, Donnie Berkholz пишет:
> On 14:24 Sun 24 Oct , William Hubbs wrote:
> > I don't like no* use flags either, for the same reason that was given
> > above. -no* is a double negative and it should be avoided.
>
> Agreed. The argument that it's removing a feature i
On Mon, Oct 25, 2010 at 7:07 PM, Arfrever Frehtes Taifersar Arahesis
wrote:
> I would like to suggest that setting Python 3.1 as main active version of
> Python be officially
> supported and recommended for Gentoo developers since 2010-12-01. Majority of
> packages supporting
> only Python 2.* h
On 14:24 Sun 24 Oct , William Hubbs wrote:
> Hi all,
>
> On Thu, Oct 21, 2010 at 12:45:01PM +0300, Eray Aslan wrote:
> > On 21.10.2010 10:30, Peter Volkov wrote:
> > > Nothing there applies here, since this USE flag has nothing to do with
> > > archs/profiles...
> >
> > which will force some
On Mon, 25 Oct 2010 15:56:50 +0200
Ulrich Mueller wrote:
> > On Mon, 25 Oct 2010, Arfrever Frehtes Taifersar Arahesis wrote:
> > 1. Support for "." characters in names of USE flags
>
> Are you aware that this would break existing programs that do regexp
> matching on USE flags? The current im
2010-10-25 15:56:50 Ulrich Mueller napisał(a):
> > On Mon, 25 Oct 2010, Arfrever Frehtes Taifersar Arahesis wrote:
>
> > 1. Support for "." characters in names of USE flags
>
> Are you aware that this would break existing programs that do regexp
> matching on USE flags?
I suggest this featur
On Mon, 25 Oct 2010 15:56:18 +0200
Arfrever Frehtes Taifersar Arahesis wrote:
> 2010-10-25 15:42:00 Ciaran McCreesh napisał(a):
> > On Mon, 25 Oct 2010 15:24:23 +0200
> > Arfrever Frehtes Taifersar Arahesis wrote:
> > > 1. Support for "." characters in names of USE flags
> >
> > If you do this,
2010-10-25 15:50:23 Peter Volkov napisał(a):
> В Пнд, 25/10/2010 в 15:37 +0200, Arfrever Frehtes Taifersar Arahesis пишет:
> > I would like to suggest that setting Python 3.1 as main active version of
> > Python be officially
> > supported and recommended for Gentoo developers since 2010-12-01. Ma
> On Mon, 25 Oct 2010, Arfrever Frehtes Taifersar Arahesis wrote:
> 1. Support for "." characters in names of USE flags
Are you aware that this would break existing programs that do regexp
matching on USE flags? The current implementation of the useq()
function in portage is probably the most
2010-10-25 15:42:00 Ciaran McCreesh napisał(a):
> On Mon, 25 Oct 2010 15:24:23 +0200
> Arfrever Frehtes Taifersar Arahesis wrote:
> > 1. Support for "." characters in names of USE flags
>
> If you do this, you'll have to either convert everything using Python
> ABIs to EAPI 4 immediately, or have
В Пнд, 25/10/2010 в 15:37 +0200, Arfrever Frehtes Taifersar Arahesis
пишет:
> I would like to suggest that setting Python 3.1 as main active version of
> Python be officially
> supported and recommended for Gentoo developers since 2010-12-01. Majority of
> packages supporting
> only Python 2.* ha
On Mon, 25 Oct 2010 15:24:23 +0200
Arfrever Frehtes Taifersar Arahesis wrote:
> 1. Support for "." characters in names of USE flags
If you do this, you'll have to either convert everything using Python
ABIs to EAPI 4 immediately, or have two sets of flag names. Won't users
get confused if they ha
I would like to suggest that setting Python 3.1 as main active version of
Python be officially
supported and recommended for Gentoo developers since 2010-12-01. Majority of
packages supporting
only Python 2.* have been prepared to work correctly in situation when Python
3.* is set as main
active
I would like to request that 2 additional features are added to EAPI="4".
These features will be needed for further development of python.eclass.
1. Support for "." characters in names of USE flags
2. Support for use.unsatisfiable and package.use.unsatisfiable files in profiles
These files would h
37 matches
Mail list logo
