First: use a macro file, not a %define, to hide abc...XYZ. If you must have
package specific macro overrides, the use %{load:...} and bury the override in
a SourceN: directive. The most important reason to use a macrofile is
readability: you can split a definition over multiple lines, unlike a
What we're trying to get around is having to do `%define
foo(abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)` so that the macro
can just handle parsing `%**` itself, and then still not being able to handle
anything that looks like a long option. That hack allows repeated arguments,
RPM has no concept of "chain building": there is only one build in the spec
file, and there is only one SRPM.
Please define whatever terms you choose to make up before using so that others
might understand your complaints.
--
You are receiving this because you are subscribed to this thread.
> @nim-nim, but isn't that just about exactly what %setup by default does?
Not really, since the chainbuilding interferes `%setup` reuse with the next
archive
People just want to align
```specfile
%somesetup -z 1
%somesetup -z 2
%somesetup -z 3
```
Like they align path or source declarations
I got an email notification about a comment that was made on this issue by
@n3npq , but I can't see it here in the github webui. Quoting his comment from
the email notification:
> FWIW, rpm -qlv used exactly the same format as cpio(1) when implemented way
> back when.
>
> Continuing that
That is indeed the case that some flags are handled by the macro processor,
while others are passed along, when -- is used to stop getopt(3) option
processing.
Long options would need a means to be specified in the macro definition, and
multiple duplicated options, and or arg types, would also
But that exposes to the macro user that some flags are handled by the rpm
argument parser and others by something else.
And that forces the macro user to use a specific flag order.
The macro user does not care about all this – that's a macro implementation
detail
--
You are receiving this
That depends on what exactly we want to achieve, I suppose. The most backwards
compatible thing and minimal impact would be passing %{_prefix} to brp-compress
and replace all /usr references with that, similarly to the datadir example
above. On Linux we could easily just go with the datadir as
...so if the point is to make the output independent of BLOCK_SIZE env variable
(which is not part of the standard btw) then -k seems to be the only choice per
standard. At least as of Linux coreutils, -k does override BLOCK_SIZE.
--
You are receiving this because you are subscribed to this
No need to bet or guess, just look at the opengroup specification I linked. -B
is just as non-standard as is -b.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@n3npq It looks like you are deleting most of your comments after posting them
here. This disrupts the discussion and renders the tickets unusable. Also note
that they are still available in the mailing-list archive and everyone's mail
folder - if you don't want your words to be archived and
Agree. The error message does not help a lot. Some additional info containing
whole %anotherluamacro can improve the situation.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
12 matches
Mail list logo
