-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-12-2010 03:02, Jorge Manuel B. S. Vicetto wrote:
> On 29-11-2010 10:34, Sebastian Pipping wrote:
> As Arfrever noted, this is likely the cause of the broken automated
> weekly stages for this past week. By not having a python symlink /
> wrapper,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29-11-2010 10:34, Sebastian Pipping wrote:
> On 11/29/10 09:35, Arfrever Frehtes Taifersar Arahesis wrote:
>> There will probably be no active version of Python set.
>
> You had two weeks to come up with this.
>
> Please find my on IRC to team up
Hi guys,
Since I just committed a rewritten ebuild for a package that was
absolutely broken in tree, I'm going to ask this nicely.
Please test what you bump.
If you cannot test it entirely because you lack the hardware, track down
somebody who does, or simply leave it alone until somebody actual
On Wed, Dec 1, 2010 at 7:16 AM, Matt Turner wrote:
> On Wed, Dec 1, 2010 at 1:25 AM, Nirbheek Chauhan wrote:
>> On Wed, Dec 1, 2010 at 6:30 AM, Diego Elio Pettenò
>> wrote:
>>> Hi all,
>>>
>>> I was wondering if we have space already, or if others would feel
>>> strongly about making space for,
On Wed, Dec 1, 2010 at 1:25 AM, Nirbheek Chauhan wrote:
> On Wed, Dec 1, 2010 at 6:30 AM, Diego Elio Pettenò
> wrote:
>> Hi all,
>>
>> I was wondering if we have space already, or if others would feel
>> strongly about making space for, maintainer notes in packages'
>> metadata.xml.
>>
> [snip]
On Wed, Dec 1, 2010 at 6:30 AM, Diego Elio Pettenò wrote:
> Hi all,
>
> I was wondering if we have space already, or if others would feel
> strongly about making space for, maintainer notes in packages'
> metadata.xml.
>
[snip]
>
> What I'm thinking of is having some sort of element,
> but not a
Hi all,
I was wondering if we have space already, or if others would feel
strongly about making space for, maintainer notes in packages'
metadata.xml.
I ask this because I was looking through some crypto based packages that
require specific hardware that seems to have been maintained "at eye
leve
On 11/29/10 16:47, Arfrever Frehtes Taifersar Arahesis wrote:
> It wasn't any mistake. Please actually read that code:
>
> eselect_python_update() {
> if [[ -z "$(eselect python show --python${PV%%.*})" ]]; then
> eselect python update --python${PV%%.*}
> fi
> }
>
> "${P
> pkg_preinst() {
> main_active_python=$(eselect python show)
> }
>
> pkg_postinst() {
> if [[ -n $main_active_python &&
> $main_active_python != $(eselect python show) ]] ; then
> einfo "restoring active python interpreter"
> eselect python se
On Tue, 30 Nov 2010 17:26:44 +0100
Sebastian Pipping wrote:
> My debugging ebuild (attached) confirms a fitting order of
> invocations:
Careful with that. The order of pre/post stuff is package manager and
EAPI dependent, thanks to Portage sneakily changing the order without
telling anyone (and w
Il giorno mar, 30/11/2010 alle 17.43 +0100, justin ha scritto:
>
> gcc is in CAT sys-devel, where icc/ifc are in dev-lang. They are both
> c/fortran compilers. Shouldn't we move icc/ifc to sys-devel?
No, it's not a system package. You don't need icc/ifc, you do need gcc
(for how Gentoo is struct
Hi all,
gcc is in CAT sys-devel, where icc/ifc are in dev-lang. They are both
c/fortran compilers. Shouldn't we move icc/ifc to sys-devel?
cheers justin
signature.asc
Description: OpenPGP digital signature
On 11/30/2010 08:26 AM, Sebastian Pipping wrote:
>* STAGE pkg_preinst (slot 2.7, version 2.7.1)
>* STAGE pkg_prerm (version 2.7, slot 2.7) <
>* STAGE pkg_postrm (version 2.7, slot 2.7) <
>* STAGE pkg_postinst (slot 2.7, version 2.7.1)
>
> Shall we give that
On 11/30/10 03:24, Zac Medico wrote:
> Yes, hopefully something like this will do it:
>
> pkg_preinst() {
> main_active_python=$(eselect python show)
> }
>
> pkg_postinst() {
> if [[ -n $main_active_python &&
> $main_active_python != $(eselect python show) ]] ; then
>
14 matches
Mail list logo
