Re: Question about sane usage of macroses in perl template

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

 



On 2010-08-27, Pavel Alexeev (aka Pahan-Hubbitus) <forum@xxxxxxxxxxxxxxx> wrote:
>
> %{__perl} Makefile.PL INSTALLDIRS=vendor
> OPTIMIZE="$RPM_OPT_FLAGS"
>
> make %{?_smp_mflags}
>
> I'm wonder why there used mix of macros %{__perl} and plain other
> commands like make?

Because you cannot have macro for each shell command. (Actually you can,
but it would be silly). Personally, I don't like aliasing macros and
I prefer direct commands as it's simpler and more readable.


> Rpm say it is just perl command with path:
> $ rpm --eval '%{__perl}'
> /usr/bin/perl
> Is there any advantage for that?
>
Probably perl interpreter had been in other location or under diferrent
name before. (E.g. transition between two incompatible perl versions).
This macro could be used to make easy the transition for package
maintainers. Or there had been used some addition perl arguments (like
-w). Or the macro was defined to allow spec file sharing between
distributions with different perl locations.

However this is just speculation. You need to ask the guy how invented
the macro. (It wasn't me :)

-- Petr

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux