Re: pkg/41275 (installed lang/parrot references build directory)

[dholland]

Synopsis: installed lang/parrot references build directory

State-Changed-From-To: open->feedback
State-Changed-By: dholland@...
State-Changed-When: Mon, 09 Nov 2009 07:05:02 +0000
State-Changed-Why:
The package has been updated several times in the last few months; does the
problem persist?

[Havard Eidnes]

> The package has been updated several times in the last few
> months; does the problem persist?

I suspect it does...  I've tried to bring this up in the parrot
community, but they say something to the effect that "you're not
supposed to use that config variable to get at the parrot lib",
and for some reason they don't think that references to the build
directory in "supposed not to be used" config variables is a bug.
I tend to differ, but it looks like I'm losing that battle.

See https://trac.parrot.org/parrot/ticket/762 and
https://trac.parrot.org/parrot/ticket/649.

Best regards,

- Håvard

[Havard Eidnes]

The following reply was made to PR pkg/41275; it has been noted by GNATS.

From: Havard Eidnes <he@...>
To: gnats-bugs@..., dholland@...
Cc: pkgsrc-bugs@..., gnats-admin@...,
 joern.clausen@...
Subject: Re: pkg/41275 (installed lang/parrot references build directory)
Date: Mon, 09 Nov 2009 10:05:47 +0100 (CET)

 > The package has been updated several times in the last few
 > months; does the problem persist?
 
 I suspect it does...  I've tried to bring this up in the parrot
 community, but they say something to the effect that "you're not
 supposed to use that config variable to get at the parrot lib",
 and for some reason they don't think that references to the build
 directory in "supposed not to be used" config variables is a bug.
 I tend to differ, but it looks like I'm losing that battle.
 
 See https://trac.parrot.org/parrot/ticket/762 and
 https://trac.parrot.org/parrot/ticket/649.
 
 Best regards,
 
 - H=E5vard