Modern POPT will collect multiple instances of an option in an argv array.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Relocations in RPM are a vestigial implementation: in fact every path can be
relocated all this century independent of whether there is one or more Prefix:
tags in a spec file.
The existence of one or more Prefix: tags controls whether a warning is
displayed (or not).
If the relocations were
Or rip out the entire relocation implementation, leaving only parsing of
Prefix: for legacy spec file syntax compatibility perhaps: the implementation
is almost entirely useless currently because of lack of persistence, and the
difficulty of propagating relocated paths into file triggers and
@Conan-Kudo: non-RedHat based distro's stubborn use of Group: and other
RPM_I18NSTRING_TYPE in spite of alternative implementations that solved real
world problems forces ancient code to be zombie marched into the future
forevermore. Distro's continuing to use Group: tags from rpm packages
> On Aug 22, 2018, at 5:01 PM, Vladimir D. Seleznev
> wrote:
>
> You convinced me that there should be whitelist filter, so I rewrote
> code for it. Follow Panu suggestion [1] I wrote .C generator to filter
> proper rpm tags. But currently it does not allow this suggestion [2] by
> jbj@:
>
>
> On Aug 22, 2018, at 5:01 PM, Vladimir D. Seleznev
> wrote:
...
>
> Also its value may be needs a prefix for versioning tag value. When new
> tags are marked to be involve to calculating the prefix changes. I think
> the prefix should also include a vendor identifier e.g. fc, alt, mga,
>
I would probably keep this, but make this change for Group tag (since that one
is deprecated and does nothing).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Almost nobody uses them, so the
"Relocations : (not relocatable)" line is a waste of screen estate.
Just output the line if there's something interesting to show.
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/532
-- Commit
Various other tags (Bugurl, etc) are shown conditionally, so I don't see why
this should not be.
I'd love to see the same change for Group, but afaics, current syntax does not
allow conditional expansion based on value.
--
You are receiving this because you are subscribed to this thread.
@ignatenkobrain Only Fedora does nothing with Group tag. Every other distro
does.
@keszybz I vaguely recall that there is some usage of Relocations, just not in
rpm with Linux, so it's good that this only shows up if there are any.
--
You are receiving this because you are subscribed to this
The problem is that unlike %setup, %autosetup is a regular macro and doesn't
really support multiple arguments of the same type - they're accepted but with
"last one wins"-semantics:
```
[pmatilai@sopuli ~]$ rpm --eval "%autosetup -N -a 1 -a 2"
%setup -a 2 -q
```
--
You are receiving
In other words, I failed to consider such a case when adding %autosetup.
The way arguments are presented in the macro language doesn't scale to such
usage, I suppose the best we can do is a workaround by passing anything after
"--" as-is to %setup which can handle those multiple repeated
12 matches
Mail list logo
