ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Andrey Cherepanov <cas@altlinux.org>
To: devel@lists.altlinux.org
Subject: Re: [devel] A: rpm-macros-ninja-build
Date: Sat, 23 May 2020 19:14:34 +0300
Message-ID: <5999e129-5491-7cfa-01d5-290ad3508050@altlinux.org> (raw)
In-Reply-To: <20200523122404.GA32767@altlinux.org>

23.05.2020 15:24, Dmitry V. Levin пишет:
> On Sat, May 23, 2020 at 08:57:08AM +0300, Andrey Cherepanov wrote:
>> 22.05.2020 22:11, Dmitry V. Levin пишет:
>>> On Tue, May 12, 2020 at 01:03:55PM +0000, Girar Builder pender robot wrote:
>>>> http://git.altlinux.org/tasks/archive/done/_245/251572/logs/events.4.2.log
>>>>
>>>> 2020-May-12 12:55:24 :: task #251572 for sisyphus resumed by cas:
>>>> #100 build 1.10.0-alt2 from /people/cas/packages/ninja-build.git fetched at 2020-May-12 08:43:36
>>> [...]
>>>> #100 ninja-build 1.10.0-alt1 -> 1.10.0-alt2
>>>>    Tue May 12 2020 Andrey Cherepanov <cas@altlinux> 1.10.0-alt2
>>>>    - Package RPM macros to main package.
>>> Я считаю, что это изменение ошибочное в принципе, поскольку затрудняет
>>> редактирование спек-файлов, в которых используются макросы из пакета
>>> rpm-macros-ninja-build, когда пакет ninja-build не установлен.
>>>
>>> Просьба вернуть пакет rpm-macros-ninja-build, и вообще больше
>>> не закапывать rpm-macros-* внутрь других пакетов.
>> Хорошо.
> Как-то странно получилось:
>
> $ rpmquery -Rp /ALT/Sisyphus/files/noarch/RPMS/rpm-macros-ninja-build-1.10.0-alt3.noarch.rpm
> /usr/lib/rpm/macros.d
> ninja-build = 1.10.0-alt3:sisyphus+252101.100.1.1
>
> Я бы понял, если бы ninja-build зависел бы от rpm-macros-ninja-build,
> но тут обратная зависимость, которая явно лишняя.
>
>
А разве не логично подтягивать по зависимости при установке макросов и 
пакет с исполняемой программой, которая в них используется в качестве 
основного компонента?

-- 
Andrey Cherepanov
cas@altlinux.org



  parent reply	other threads:[~2020-05-23 16:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 19:11 ` Dmitry V. Levin
2020-05-23  5:57   ` Andrey Cherepanov
2020-05-23 12:24     ` Dmitry V. Levin
2020-05-23 15:24       ` Alexey V. Vissarionov
2020-05-23 16:14       ` Andrey Cherepanov [this message]
2020-05-23 17:00         ` Dmitry V. Levin
2020-05-23 19:13           ` Andrey Cherepanov
2020-05-23 19:24             ` Alexey Gladkov
2020-05-24 13:21               ` Vitaly Lipatov
2020-05-24 20:16                 ` Dmitry V. Levin
2020-05-24 21:30                   ` Andrey Savchenko
2020-05-25  4:15                     ` Michael Shigorin
2020-05-25  6:23                       ` Andrey Savchenko
2020-05-25 12:24               ` Aleksey Cheusov
2020-05-25 12:40                 ` Dmitry V. Levin
2020-05-25 13:18                   ` Aleksey Cheusov
2020-05-25 12:53                 ` Alexey Gladkov
2020-05-25 13:07                   ` Anton Farygin
2020-05-25 13:09                     ` Dmitry V. Levin
2020-05-25 14:02                       ` Anton Farygin
2020-05-25 13:20                   ` Aleksey Cheusov
2020-05-25 14:15                     ` Dmitry V. Levin
2020-05-25 14:22                     ` Alexey Gladkov
2020-05-25 14:25                       ` Anton Farygin
2020-05-25 14:35                         ` Alexey Gladkov
2020-05-25 14:48                           ` Anton Farygin
2020-05-25 15:17                             ` Alexey Gladkov
2020-05-26  6:36                               ` Anton Farygin
2020-05-26  9:10                                 ` Alexey Gladkov
2020-05-26 11:22                                   ` Anton Farygin
2020-05-26 11:57                                     ` Alexey Gladkov
2020-05-26 13:47                                       ` Anton Farygin
2020-05-26 14:56                                         ` Andrey Savchenko
2020-05-26 18:02                                           ` Anton Farygin
2020-05-26 14:37                               ` Sergey V Turchin

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=5999e129-5491-7cfa-01d5-290ad3508050@altlinux.org \
    --to=cas@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