From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] javatoolkit: new project layout
Date: Tue, 08 Jan 2008 01:33:33 +0200 [thread overview]
Message-ID: <4782B6CD.3090003@gentoo.org> (raw)
In-Reply-To: <20080107204204.GG21604@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
Fabian Groffen kirjoitti:
> On 07-01-2008 22:29:46 +0200, Petteri Räty wrote:
>> Fabian Groffen kirjoitti:
>>> would it be possible to do it like we do it in Portage?
>>>
>>> sys.path.insert(0, os.path.join(os.path.dirname(os.path.dirname(os.path. realpath(__file__))), "pym"))
>>>
>> Or we could just depend on a new enough Portage where just import portage
>> works. This probably works in prefix too?
>
> Well... one can only do "import portage" if one's really sure one uses a
> Gentoo patched python. (Admittedly this is in general the case.)
> Portage code itself uses a guard to extend the python path in case the
> import fails.
>
> However, doing "import portage" slows you down a lot, so if you don't
> really need it, I would disadvice to do it.
>
>>> The globs in findclass I guess we'll have to patch in the prefix case,
>>> though I'm wondering if that doesn't need ROOT support anyway?
>>> If you'd really want to make be happy you'd do a
>>> try:
>>> from portage.const import EPREFIX
>>> catch ImportError:
>>> EPREFIX = ''
>>>
>>> pkg = glob.glob(EPREFIX + '/usr/share/*/package.env')
>> Well you build against the stuff in / so ROOT should not be used I think.
>
> I'm not sure how much root support works in Java. I just imagined that
> you'd run the tool on a chroot or something.
>
Yeah but in chroot you would of course use /
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2008-01-07 23:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 12:16 [gentoo-java] javatoolkit: new project layout Alistair Bush
2008-01-05 12:31 ` Fabian Groffen
2008-01-05 21:29 ` Alistair Bush
2008-01-07 20:19 ` Fabian Groffen
2008-01-07 20:29 ` Petteri Räty
2008-01-07 20:42 ` Fabian Groffen
2008-01-07 23:33 ` Petteri Räty [this message]
2008-01-08 8:44 ` Fabian Groffen
2008-01-08 6:13 ` Alistair Bush
2008-01-08 8:47 ` Fabian Groffen
2008-01-09 8:49 ` Alistair Bush
2008-01-09 9:04 ` Alistair Bush
2008-01-10 5:46 ` Alistair Bush
2008-01-10 21:31 ` Vlastimil Babka
2008-01-10 23:51 ` Petteri Räty
2008-01-05 12:40 ` Vlastimil Babka
2008-01-05 21:46 ` Alistair Bush
2008-01-05 23:06 ` Alistair Bush
2008-01-05 23:21 ` Vlastimil Babka
2008-01-05 23:44 ` Petteri Räty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4782B6CD.3090003@gentoo.org \
--to=betelgeuse@gentoo.org \
--cc=gentoo-java@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox