Luca Barbato wrote:
Carsten Lohrke wrote:
On Sunday 03 September 2006 16:36, Stefan Schweizer wrote:
I am not adding stuff. I am fixing existing packages. And I am taking
responsibility.
How wonderful this sort of maintenance is you can read here:
On 9/7/06, Carsten Lohrke [EMAIL PROTECTED] wrote:
How wonderful this sort of maintenance is you can read here:
https://bugs.gentoo.org/show_bug.cgi?id=146626
Am I the only one who has a problem with this?
No. And I'm sure I'm not the only one who has a problem with your
comment in that bug
Am Donnerstag, 7. September 2006 11:11 schrieb Stuart Herbert:
On 9/7/06, Carsten Lohrke [EMAIL PROTECTED] wrote:
How wonderful this sort of maintenance is you can read here:
https://bugs.gentoo.org/show_bug.cgi?id=146626
Am I the only one who has a problem with this?
No. And I'm
On Thu, Sep 07, 2006 at 12:17:27PM +0200, Danny van Dyk wrote:
Am Donnerstag, 7. September 2006 11:11 schrieb Stuart Herbert:
On 9/7/06, Carsten Lohrke [EMAIL PROTECTED] wrote:
How wonderful this sort of maintenance is you can read here:
https://bugs.gentoo.org/show_bug.cgi?id=146626
Alec Warner wrote:
If you can't work
it out, you talk to your project lead. If THEY can't work it out, you
talk to the ombudsman, and so forth. Everyone knows the policy and yet
no one follows it. I don't want to see this thread continue; you know
what you have to do.[1]
[1]
Brian Harring wrote:
On Wed, Sep 06, 2006 at 10:37:21PM -0400, Stephen P. Becker wrote:
Carsten Lohrke wrote:
On Sunday 03 September 2006 16:36, Stefan Schweizer wrote:
I am not adding stuff. I am fixing existing packages. And I am taking
responsibility.
How wonderful this sort of
On Thursday 07 September 2006 04:09, Carsten Lohrke wrote:
How wonderful this sort of maintenance is you can read here:
I'll try to overlook the reverted changes in kdelibs for bug fixes, the
improper ${ROOT} injected in my changes where it wasn't supposed to be, the
broken opengl on kdelibs
On Thursday 07 September 2006 07:58, Stefan Schweizer wrote:
I am part of the kde herd, thanks.
To my knowledge you have never asked to join the KDE team, nor did I see you
helping tracking down KDE bug reports ever. Just adding yourself doesn't
work.
Carsten
pgp7tjbj1KWLV.pgp
Stephen P. Becker wrote:
Brian Harring wrote:
The proper forum for crap like this is via taking it up with QA/devrel.
Screaming about a change on the ml doesn't accomplish anything more
then making you look like a jack ass trying to publically embarass
someone you're pissed at; at least
On Thursday 07 September 2006 13:25, Diego 'Flameeyes' Pettenò wrote:
I'll try to overlook the reverted changes in kdelibs for bug fixes, the
improper ${ROOT} injected in my changes where it wasn't supposed to be, the
broken opengl on kdelibs checks that appeared last month, unhelpful
comments
On Thursday 07 September 2006 13:48, Jakub Moc wrote:
I wonder how exactly genstef broke mips, 'cos mind you, he just reverted
to what the ebuild was doing before Bug 114161 was fixed by
hard-disabling of hspell [1]. Since mips doesn't have hspell keyworded,
it wasn't affected by that bug
Carsten Lohrke wrote:
One question remains: Is it needed/correct that Portage doesn't take blockers
for architecture breakages into account? Such a line/prefix is easily changed
and when someone - whatever the bad reason is - uses cvs commit, a real tree
breakage is the cause.
The
On Wed, 2006-09-06 at 23:50 -0400, Curtis Napier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: MD5
I'm in support of having a list of devs who want to do paid support.
Anything that helps people eat is OK in my book. ;)
On the other hand, I think we need to have the foundation run this
Simon Stelling wrote:
Carsten Lohrke wrote:
One question remains: Is it needed/correct that Portage doesn't take
blockers
for architecture breakages into account? Such a line/prefix is easily
changed
and when someone - whatever the bad reason is - uses cvs commit, a real tree
breakage
Jakub Moc wrote:
carlo, you might want to revert it properly, instead of reverting only
half of the previous commit you've been complaining about here.
Could you please take such stuff where it belongs next time? (To the
bug, that is.) There's really no need to point out such things on -dev,
On Thu, 07 Sep 2006 16:42:11 +0200
Simon Stelling [EMAIL PROTECTED] wrote:
Carsten Lohrke wrote:
One question remains: Is it needed/correct that Portage doesn't
take blockers for architecture breakages into account? Such a
line/prefix is easily changed and when someone - whatever the bad
What have we learnt now, Jakub? Keep it in the bug report. ;)
Carsten
pgpxG13G6keIP.pgp
Description: PGP signature
Carsten Lohrke wrote:
On Thursday 07 September 2006 16:42, Simon Stelling wrote:
!app-text/hunspell-1.0, which means that you can't have hunspell-1.0
and kdelibs installed on a system at the same time.
This is clear to me. My point was, if there's a specific need to allow to not
to break
Hi guys,
We are planning to add git.eclass as presented in bug #132383 (as
attachment 96300). I also attach it here in case someone wants to
comment parts of it.
Please raise your concerns if you have any.
- ferdy
--
Fernando J. Pereda Garcimartín
Gentoo Developer (Alpha,net-mail,mutt,git)
On Thursday 07 September 2006 20:31, Chris White wrote:
So, wondering why people use Gentoo.
penis envy
-mike
pgpD0ckVyufBA.pgp
Description: PGP signature
[user]
I started using gentoo on dec. 2003. This was my first big step after one year SuSE Linux. I was very delight when I
saw, that I was able to build my own system (I always wanted it) with my own requirements and in the way I wanted it to
be built. I was very happy when I didn't saw the
So, wondering why people use Gentoo. Put [dev] or something if you're an
actual gentoo dev and [user] if you're a user. Doesn't need to be fancy, you
can put community or something if that's all you want. All responses off
list please. Thanks.
--
Chris White
Gentoo Developer
A+ | MCSE
Zac Medico wrote:
If we implement the repo-level profile, it can have a
bashrc (much like profile.bashrc) that acts as a repo-level ebuild template
(like install-helpers.eclass). Actually, the repo-level profile already
exists
in the form of files such as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Stelling wrote:
repo-level profile, we move parts of the EAPI out into the tree, which
is a bad idea because we are unable to support multiple versions. As the
EAPI needed for the ebuild is unknown when sourcing
install-helpers.eclass, we're
On Thu, Sep 07, 2006 at 09:32:04AM -0700, Zac Medico wrote:
Simon Stelling wrote:
repo-level profile, we move parts of the EAPI out into the tree, which
is a bad idea because we are unable to support multiple versions. As the
EAPI needed for the ebuild is unknown when sourcing
Zac Medico wrote:
Well, if the metadata generation step is viewed as being separate from the
rest,
and the helpers aren't needed during that step, then it's possible to get the
EAPI from the ebuild without the helpers being in the environment. Once the
EAPI is known, the package manager can
Brian Harring wrote:
Make this change, and it means that all overlays that can function as
standalone, must bundle the eapi helpers themselves.
Not true. I don't have to add eutils.eclass to my overlay to use epatch.
Same goes for install-helpers.eclass. Standalone-repos will have that
On Thu, Sep 07, 2006 at 07:11:01PM +0200, Simon Stelling wrote:
Brian Harring wrote:
Make this change, and it means that all overlays that can function as
standalone, must bundle the eapi helpers themselves.
Standalone-repos will have that
problem, but there is none yet to my knowledge.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Stelling wrote:
Brian Harring wrote:
B) fragmentation this implicitly enables
isn't good.
I agree here.
Fragmentation is always a potential with free and open software. People can
fork if they want or collaborate if they want. The
On Thu, Sep 07, 2006 at 10:22:38AM -0700, Zac Medico wrote:
Simon Stelling wrote:
Zac Medico wrote:
Well, if the metadata generation step is viewed as being separate from the
rest,
and the helpers aren't needed during that step, then it's possible to get
the
EAPI from the ebuild
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Stelling wrote:
Zac Medico wrote:
Well, if the metadata generation step is viewed as being separate from the
rest,
and the helpers aren't needed during that step, then it's possible to get the
EAPI from the ebuild without the helpers being
31 matches
Mail list logo
