On 04/23/2010 08:14 AM, James Cloos wrote:
>> "HvD" == Harald van Dijk writes:
>
> HvD> Let's say this is in the tree:
>
> HvD> foo.eclass:
> HvD> DEPEND="dev-lang/python:2.6"
>
> HvD> bar-1.ebuild:
> HvD> inherit foo
>
> HvD> Let's say this is in your overlay:
>
> HvD> foo.eclass:
> HvD>
On Sat, 24 Apr 2010 22:42:58 +0200
Michał Górny wrote:
> The hack bypasses the whole concept of PM package stabilization - it
> 'injects' the bash code into every version of Portage, pkgcore
> and Paludis (I guess). A code targeted at Portage, I'd add.
Paludis doesn't use bashrc from profiles pre
Hello,
I would like to raise a discussion on the topic of the /etc/portage/env
files support hack, implemented in the profile.bashrc file in gx86 base
profile [1].
I am working on the portage-side implementation of the feature and I
would like to avoid double-sourcing of the override files. Altho
On Sat, 24 Apr 2010 20:40:54 +0300
Petteri Räty wrote:
> 17:34 < Betelgeuse> robbat2|na: how easy to it to prevent commits to
> CVS if the commit message doesn't match a certain pattern?
> 17:36 <@robbat2|na> go and checkout the CVSROOT and there should be an
> example there
> 17:37 < Betelgeuse>
On 24 April 2010 23:10, Petteri Räty wrote:
> 17:34 < Betelgeuse> robbat2|na: how easy to it to prevent commits to CVS
> if the commit message doesn't match a certain pattern?
> 17:36 <@robbat2|na> go and checkout the CVSROOT and there should be an
> example there
> 17:37 < Betelgeuse> robbat2|na:
17:34 < Betelgeuse> robbat2|na: how easy to it to prevent commits to CVS
if the commit message doesn't match a certain pattern?
17:36 <@robbat2|na> go and checkout the CVSROOT and there should be an
example there
17:37 < Betelgeuse> robbat2|na: Ok so doable then. Thanks.
What do you think about no
