public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel Pielmeier" <daniel.pielmeier@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] media-video/totem-2.20.3 Access violation
Date: Wed, 30 Jul 2008 10:06:38 +0200	[thread overview]
Message-ID: <6142e6140807300106u28de49c3u720bd770dd49c0ca@mail.gmail.com> (raw)
In-Reply-To: <48900B58.6020601@yahoo.com.br>

All the problems above are related to python byte code, and the way it
is handled in gentoo. It would be to exhaustive to explain the
problems here but maybe this bug [1] helps to understand the problem.
Also if you want to learn more about python in gentoo you can read
this [2].

In the case of scons and docbook the problem is the same as mentoned
in the bug where python bytecode is installed into the wrong
filesystem location.

Other problems can occur when the python eclasses which handle the
python byte code are not used at all or improperly used with python
applications. For instance when python byte code is not handled by the
eclasses the py{c,o} files are created at runtime when using the
program as root. At deinstallation this files are not removed from the
filesystem because the package manager is not aware of them.

[1] http://bugs.gentoo.org/show_bug.cgi?id=194343
[2] http://www.gentoo.org/proj/en/Python/developersguide.xml



      reply	other threads:[~2008-07-30  8:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 19:44 [gentoo-user] media-video/totem-2.20.3 Access violation Ivan Alden
2008-07-21 10:34 ` Markus Schönhaber
2008-07-22 12:17   ` Ivan Alden
2008-07-22  9:17     ` Markus Schönhaber
2008-07-29 15:50 ` Alex Schuster
2008-07-30  6:34 ` Zhu Sha Zang
2008-07-30  8:06   ` Daniel Pielmeier [this message]

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=6142e6140807300106u28de49c3u720bd770dd49c0ca@mail.gmail.com \
    --to=daniel.pielmeier@googlemail.com \
    --cc=gentoo-user@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