On Wed, 07 Mar 2012 08:00:16 +0100
Paweł Hajdan, Jr. phajdan...@gentoo.org wrote:
Also the inter-bug dependencies are often not resolved correctly,
that is the to be keyworded package depends on non-keyworded stuff
not listed in the bug.
And this is even worse. Please check things with
On 09:25 Wed 07 Mar 2012, Alexis Ballier wrote:
On Wed, 07 Mar 2012 08:00:16 +0100
Paweł Hajdan, Jr. phajdan...@gentoo.org wrote:
Also the inter-bug dependencies are often not resolved correctly,
that is the to be keyworded package depends on non-keyworded stuff
not listed in the bug.
On Wed, 7 Mar 2012 15:54:49 +0100
Thomas Kahle to...@gentoo.org wrote:
On 09:25 Wed 07 Mar 2012, Alexis Ballier wrote:
On Wed, 07 Mar 2012 08:00:16 +0100
Paweł Hajdan, Jr. phajdan...@gentoo.org wrote:
Also the inter-bug dependencies are often not resolved
correctly, that is the to be
On Tue, 2012-03-06 at 23:17 +0100, Thomas Kahle wrote:
Ruby is an interpreted language, I don't see any
point in having every arch team do the testing for every small package.
Could the ruby team add ~x86 themselves after testing on ~amd64, or are
there compelling reasons to not do this?
On Wed, 2012-03-07 at 08:00 +0100, Paweł Hajdan, Jr. wrote:
It's trivial to set up x86 chroot on amd64 box, so I can't imagine
what's preventing people from creating such chroot, doing the testing
and keywording themselves.
In my personal case what is preventing me is sheer and utter
Hi all,
The way how we currently specify the EAPI in ebuilds has some
problems. For example, there is no sane way to allow usage of features
of a new bash version in a new EAPI. So we are currently stuck with
bash 3.2. Also changes of global scope behaviour, like addition of new
global scope
On Wed, 7 Mar 2012 21:41:02 +0100
Ulrich Mueller u...@gentoo.org wrote:
(I really hope for a constructive discussion here. So, if you want
to comment that all of the above proposals suck and GLEP 55 is much
superior, then please open a new thread for it.)
I think if you want a constructive
On Wed, 7 Mar 2012 21:41:02 +0100
Ulrich Mueller u...@gentoo.org wrote:
Hi all,
The way how we currently specify the EAPI in ebuilds has some
problems. For example, there is no sane way to allow usage of features
of a new bash version in a new EAPI. So we are currently stuck with
bash 3.2.
On 7 March 2012 21:07, Alexis Ballier aball...@gentoo.org wrote:
As i understand it, $PM will need to try the regexp tingy on any ebuild
anyway, guess the EAPI then source the ebuild with the right sourcer
to get the real EAPI and compare it.
Not exactly... the idea with proposal 2) is that
On 03/07/2012 03:41 PM, Ulrich Mueller wrote:
*** Proposal 2: EAPI in header comment ***
A different approach would be to specify the EAPI in a specially
formatted comment in the ebuild's header. No syntax has been suggested
yet, but I believe that the following would work as a specification:
On Wed, 2012-03-07 at 21:41 +0100, Ulrich Mueller wrote:
.ebuild - .eb
FYI, any Russian speaker is *guaranteed* to read the name .eb as a
very common obscenity.
On Wed, 07 Mar 2012, Michael Orlitzky wrote:
Someone suggested using a standard shebang the last time this came
up, and if I remember correctly it was one of the least-disagreeable
solutions proposed. We could of course define our own custom format,
but I think something like,
On Wed, 07 Mar 2012 17:36:05 -0500
Alexandre Rostovtsev tetrom...@gentoo.org wrote:
FYI, any Russian speaker is *guaranteed* to read the name .eb as a
very common obscenity.
In Dutch it means the low tide, and as a verb, it means becoming low
or decreasing as in the tide or some other fluid.
On Wed, Mar 7, 2012 at 12:41 PM, Ulrich Mueller u...@gentoo.org wrote:
Hi all,
The way how we currently specify the EAPI in ebuilds has some
problems. For example, there is no sane way to allow usage of features
of a new bash version in a new EAPI. So we are currently stuck with
bash 3.2.
On Wed, Mar 07, 2012 at 11:38:47PM -0600, Donnie Berkholz wrote:
http://wiki.gentoo.org/wiki/Google_Summer_of_Code/2012/Ideas. If you
have project ideas, this is the place to put them. It's critical to also
include potential mentors and prerequisite skills so students know which
ideas make
On Wed, 7 Mar 2012, Alec Warner wrote:
*** Proposal 1: Parse the EAPI assignment statement ***
[...]
I don't like this idea because the sane way should be easy and
straightforward. Mixing a constant declaration with bash assignment
just confuses users who think the assignment is full bash
I am not a developer yet, but I would like to suggest some idea possibilities:
Minix port of Gentoo
Illumos port of Gentoo
LLVM/Clang System Compiler Support
ICC System Compiler Support (probably easier than LLVM/Clang)
Port of Gentoo/FreeBSD to amd64 (or other architectures)
Gentoo/FreeBSD KVM
17 matches
Mail list logo
