ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: "Евгений Ростовцев" <real.altlinux.org@gmail.com>
Cc: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] Q: python default byte-compilation paths list
Date: Wed, 17 Feb 2010 16:54:07 +0300
Message-ID: <20100217135406.GA26455@wo.int.altlinux.org> (raw)
In-Reply-To: <8d778a621002162259yad0ea65g6854d55c66e8eb77@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

On Wed, Feb 17, 2010 at 01:59:15PM +0700, Евгений Ростовцев wrote:
> > Я посмотрел, где, помимо %_target_libdir/python%__python_version и
> > %_target_libdir_noarch/python%__python_version, у нас в Сизифе
> > встречаются модули для python, и обнаружил следующее:
> 
> Таких мест много, а разве %add_python_lib_path действует только во
> время сборки?

В пакет он, по крайней мере, не зашивается.  Но использовать
%_python_lib_path ещё и для для байт-компиляции -- эта идея
кажется мне правильной.


-- 
ldv

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2010-02-17 13:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  1:27 ` [devel] Q: python x86_64 (was: [#20176] FAILED srpm=postr-0.12.4-alt1.src.rpm) Dmitry V. Levin
2010-02-16  2:23   ` Yuri N. Sedunov
2010-02-16  2:43     ` [devel] Q: python x86_64 Dmitry V. Levin
2010-02-16  9:12       ` Евгений Ростовцев
2010-02-16 14:55         ` Dmitry V. Levin
2010-02-17  0:09           ` [devel] Q: python default byte-compilation paths list compilation Dmitry V. Levin
2010-02-17  6:59             ` Евгений Ростовцев
2010-02-17  7:18               ` Andrey Rahmatullin
2010-02-17 14:01                 ` Dmitry V. Levin
2010-02-17 14:06                   ` Andrey Rahmatullin
2010-02-17 13:54               ` Dmitry V. Levin [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=20100217135406.GA26455@wo.int.altlinux.org \
    --to=ldv@altlinux.org \
    --cc=devel@lists.altlinux.org \
    --cc=real.altlinux.org@gmail.com \
    /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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git