On Tue, Jul 26, 2022 at 5:18 AM Marián Konček wrote:
> I would still do something about the manually expanded %mvn_install macro.
>
> Is it a big problem to have the java artifacts placed into a
> "anrlt4-project" directory?
>
> If nothing else, maybe you could rpm --eval %%mvn_install | sed '-n
There is no right or wrong, I just saw this as unusual.
I see this is a complex package and you went through some decision
process when deciding on this.
I would still do something about the manually expanded %mvn_install macro.
Is it a big problem to have the java artifacts placed into a
On Tue, Jul 26, 2022 at 11:08 AM Marián Konček wrote:
>
> I used a wrong mailing list, I meant to send it here.
>
> I still see this approach as wrong. You can change the archfulness of
> the main package. You can add a -java subpackage which is noarch and
> provides the main package name for
I used a wrong mailing list, I meant to send it here.
I still see this approach as wrong. You can change the archfulness of
the main package. You can add a -java subpackage which is noarch and
provides the main package name for example. In the .spec I see you
manually invoke expanded
