ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Leonid Krivoshein <klark.devel@gmail.com>
To: devel@lists.altlinux.org
Subject: Re: [devel] Policy на порядок полей в спеке
Date: Fri, 30 Oct 2020 01:18:44 +0300
Message-ID: <687e3bb5-ffd6-6013-f99e-97b8fb15c250@gmail.com> (raw)
In-Reply-To: <47a82581e6242b5a2f72c60e36883aa1@altlinux.ru>


29.10.2020 23:16, Vitaly Lipatov пишет:
> Dmitry V. Levin писал 29.10.20 21:24:
> ...
>> Кажется, Source и Patch во всех вариантах идёт после Url.
>> Или нет?
> На вики был написан неправильный порядок. Исправленный вариант:
>
> ```
> Name
> Version
> Release
> Epoch
>
> Summary
>
> License
> Group
> Url
>
> Packager
>
> Source
> Patch
>
> BuildArch
> ExcludeArch
> ExclusiveArch
>
> AutoReq | AutoProv
>
> Provides
> Requires
> Conflicts
>
> BuildRequires(pre)
> BuildRequires
> ```
>
>
> Среди всех спеков (17,7 тысяч) я насчитал 3 тысячи вариантов порядка 
> тэгов, из них самые популярные:

Уверены, что порядок полей в спеке действительно имеет важное значение?

К слову, в наших спеках Vendor проставляет сборочница (rpm-build?), в 
сторонних/партнёрских там чаще встречаются другие значения. Его нет в 
этом списке. Наверняка нет чего-то ещё.

Потом, AutoReq/AutoProv из той же серии, что:

%set_verify_elf_method
%set_verify_info_method
%set_findprov_skiplist
%set_debuginfo_skiplist
%set_fixup_skiplist

Может, в каких-то ситуациях их все логичнее видеть в начале спека?


>    1797 Name Version Release Summary License Group Url Source
>    1298 Name Version Release Summary License Group Url Packager Source
>     561 Name Version Release Summary Group License Url Source
>     485 Group Name Version Release Summary License Group
>     481 Name Version Release Summary License Group Url Packager Source 
> Requires
>     463 Name Version Release Summary License Group Source
>     457 Name Version Release Summary License Group Url
>     389 Name Version Release Summary License Group Packager Source
>     366 Name Version Release Summary License Group Url Source Requires
>     315 Name Version Release Summary Group License
>     305 Name Version Release Summary License Group
>     286 Group Name Version Release Summary License
>     275 Name Version Release Summary License Group Url Packager
>     264 Name Version Release Group Summary Url License Source
>     236 Name Version Release Summary Group License Url
>     207 Name Version Release Summary License Group Url Source Packager
>     172 Name Version Release Summary License Group Url Packager Source 
> Patch
>     172 Name Version Release Summary Group License Url Packager Source
>     153 Name Version Release Summary License Group Url Source Patch
>     146 Name Version Release Summary Group License Url Source Requires
>     135 Group Name Summary Version Release Source License Requires
>     132 Name Version Release License Packager Group Url Source Patch 
> Summary
>     125 Group Name Version Release Summary License Requires
>     122 Name Version Release Summary Group License Source
>     120 Epoch Group Name Version Release Summary License
>     115 Name Version Release Summary License Group Url Vcs Packager 
> Source Obsoletes Provides
>     109 Name Version Release Summary License Group Source Requires
>     107 Group Name Version Release Summary License Requires Group
>     104 Name Version Release Summary License Group Packager
>     103 Name Version Release Summary Group License Requires
>     100 Name Version Release Summary License Group Url Requires
>
>
>

-- 
Best regards,
Leonid Krivoshein.



  reply	other threads:[~2020-10-29 22:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 16:04 Vitaly Lipatov
2020-10-29 16:33 ` Dmitry V. Levin
2020-10-29 17:23   ` Vitaly Lipatov
2020-10-29 18:24     ` Dmitry V. Levin
2020-10-29 20:16       ` Vitaly Lipatov
2020-10-29 22:18         ` Leonid Krivoshein [this message]
2020-10-30  7:45           ` Sergey V Turchin
2020-10-30  8:22             ` Anton Farygin
2020-10-30  7:44         ` Sergey V Turchin
2020-10-30  7:54         ` Andrey Cherepanov
2020-10-30  8:13           ` Sergey V Turchin
2020-10-30  8:26               ` Sergey V Turchin
2020-10-30 11:06           ` Vitaly Lipatov

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=687e3bb5-ffd6-6013-f99e-97b8fb15c250@gmail.com \
    --to=klark.devel@gmail.com \
    --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