Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Put all Perl-related macros in a single file. #37

Closed
wants to merge 2 commits into from
Closed

Put all Perl-related macros in a single file. #37

wants to merge 2 commits into from

Conversation

ascherer
Copy link
Contributor

If the %perl_... macros are %defined in macros[.in], they are automatically loaded on startup, so %includeing the extra macros.perl in the spec file is redundant.

In case that the %perl_... macros are sufficiently important to be %defined automatically on startup, the separate file macros.perl can savely be removed from the distribution.

Andreas Scherer added 2 commits January 13, 2016 16:09
If the '%perl_...' macros are '%define'd in 'macros[.in]', they are
automatically loaded on startup, so '%include'ing the extra
'macros.perl' in the spec file is redundant.

In case that the '%perl_...' macros are sufficiently important to be
'%define'd automatically on startup, the separate file 'macros.perl' can
savely be removed from the distribution.
Put _all_ Perl stuff into 'macros.perl'.
@ffesti
Copy link
Contributor

ffesti commented Jan 28, 2016

Not sure if those macro can just be hidden away. We'd need to check how much packages this is going to break before doing such a change.

It might be necessary to go the opposite direction (including the macros.perl unconditionally) and leave removing it again to the distros.

@ascherer
Copy link
Contributor Author

Personally, I don't use the Perl macros, but I know of at least this project that makes use of macros.perl. (I suggested to use %_rpmconfigdir for the lookup path.)

@ffesti
Copy link
Contributor

ffesti commented Mar 4, 2016

Looks like those macros are being used to build some packages and just removing them is probably not an option for now. Still I think you have a very valid point in that the macros are a mess and deserve cleaning up. See rpm-ecosystem ML for a broader discussion on the topic.

Closing.

@ffesti ffesti closed this Mar 4, 2016
@ascherer
Copy link
Contributor Author

ascherer commented Mar 4, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants