From: Alexey Morozov <alex-altlinux@idisys.iae.nsk.su> To: ALT Devel discussion list <devel@altlinux.ru> Subject: Re: [devel] RFC: Правильная схема построения питон-модулей Date: Thu, 12 Feb 2004 18:55:36 +0600 Message-ID: <20040212125536.GL16285@pyro.hopawar.private.net> (raw) In-Reply-To: <20040212022455.GA23100@localhost.localdomain> [-- Attachment #1: Type: text/plain, Size: 477 bytes --] В аттачменте находится поправленный файл макросов для python. Изменения: * решена проблема с именованием пакетов, если версия питон не задана явно. Теперь пакет все равно будет называться pythonXY-module... * всегда проставляется соответствующий Requires: python = X.Y * чуть более внятная диагностика ошибки при попытке сказать rpmbuild -ba pyModule.spec --with python22 --with python23 Комментарии принимаются. С радостью. Я бы даже сказал, с нетерпением :-) [-- Attachment #2: python --] [-- Type: text/plain, Size: 1309 bytes --] # for an unknown reason %%error macro doesn't lead to immediate immediate abort # so we use BuildConflicts below as a headshot :-/ %check_python_version_internal() \ %{expand: %{expand:%%{?_with_python%{2}:%%{?__python_package_version:%%%%{error:Only one python version can be selected at a time}}}}} \ %(echo %{expand:%%{?_with_python%{2}:%%{?__python_package_version:BuildConflicts: python = %{1}}}}) \ %(echo %{expand:%%{?_with_python%{2}:BuildPreReq: python = %{1}}}) \ %{expand: %{expand:%%{?_with_python%{2}:%%%%global __python %(which python%1 2>/dev/null || echo `which python`)}}} \ %{expand: %{expand:%%{?_with_python%{2}:%%{!?__python_package_version:%%%%global __python_package_version %2}}}} %check_python_version() \ %{expand: %%check_python_version_internal %{1} %(echo %1 | sed -e 's/\\.//g')} %setup_python_module() \ %{expand: %%global modulename %{1}} \ %(echo Provides: python-%{1} = %version-%release) \ %check_python_version 2.2 \ %check_python_version 2.4 \ %check_python_version 2.3 \ %{expand: %{expand: %%{!?__python_package_version:%%%%global __python_package_version %%(echo %%__python_version | tee -a aaa.log | sed -e 's/\\.//g')}}} \ %{expand: %%global packagename python%%{__python_package_version}-%%{modulename}} \ %(echo %{expand:Requires: python = %%__python_version})
prev parent reply other threads:[~2004-02-12 12:55 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-12 2:24 Alexey Morozov 2004-02-12 12:55 ` Alexey Morozov [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=20040212125536.GL16285@pyro.hopawar.private.net \ --to=alex-altlinux@idisys.iae.nsk.su \ --cc=devel@altlinux.ru \ /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