From: Mikhail Zabaluev <mhz@altlinux.org>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] Макросы в %changelog
Date: Tue, 14 Mar 2006 02:17:52 +0300
Message-ID: <1142291872.4125.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20060313225333.GA3561@basalt.office.altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
В Втр, 14/03/2006 в 01:53 +0300, Dmitry V. Levin пишет:
> > Кстати, по этой же причине нежелательно использовать макросы в
> > Provides/Obsoletes.
>
> В этом тоже иногда есть смысл, например,
> Provides: name = %serial:%version-%release
> Obsoletes: name < %serial:%version-%release
Верно. Я должен был уточнить: макросы в именах пакетов.
> Зачастую очень вредны макроконструкции, влияющие на сборочные зависимости и/или
> на саму возможность выполнения -bs --nodeps.
rpm-build-python? :)
[-- Attachment #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-03-13 23:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 6:46 ` [devel] Макросы в %changelog ([Sisyphus-cybertalk] I: Sisyphus-20060313 packages: +2 (5379)) Mikhail Zabaluev
2006-03-13 8:47 ` Sergey Y. Afonin
2006-03-13 9:24 ` Andrey Rahmatullin
2006-03-13 10:54 ` Sergey Y. Afonin
2006-03-13 11:18 ` Led
2006-03-13 12:06 ` Sergey Y. Afonin
2006-03-13 19:17 ` Andrey Rahmatullin
2006-03-13 19:31 ` Sergey Y. Afonin
2006-03-13 8:57 ` [devel] [JT] " Michael Shigorin
2006-03-13 10:57 ` [devel] " Sergey Y. Afonin
2006-03-13 13:07 ` Dmitry V. Levin
2006-03-13 22:16 ` Mikhail Zabaluev
2006-03-13 22:53 ` [devel] Макросы в %changelog Dmitry V. Levin
2006-03-13 23:17 ` Mikhail Zabaluev [this message]
2006-03-13 23:25 ` [devel] Макросы где надо и где не надо Dmitry V. Levin
2006-03-13 23:45 ` Mikhail Zabaluev
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=1142291872.4125.4.camel@localhost.localdomain \
--to=mhz@altlinux.org \
--cc=devel@lists.altlinux.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
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