Re: python-macros review

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "VO" == Vít Ondruch <vondruch@xxxxxxxxxx> writes:

VO> You can get rid of these macros for SRPM build typically just by
VO> replacing %{my_macro} by %{?my_macro}, i.e. adding just single
VO> question mark.

Some of them, but not all of them.  Think of what happens when you do:

BuildRequires: %{py3_versions}

How will conditional evaluation help that?

Yes, we could do %{?py3_dependencies}, and maybe we would, but even then
the extra ? notation is odd and easy to miss.  I'd like to reduce the
need for that kind of thing, not increase it.

Besides, the cost is pretty close to zero (not even any new packages if
the files are placed in redhat-rpm-config) so I don't see the need
here.  I do, however, disagree with the practice of having an unbounded
number of packages we have to stuff in the buildroot, each containing
one macro file.

In the currently running FPC meeting proposed having fedora-rpm-macros
or fedora-rpm-config or something where we can collect these.

 - J<
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/packaging@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux