On 03/06/2012 09:07 PM, Paul Howarth wrote:
On 03/06/2012 03:11 AM, Vijay N. Majagaonkar wrote:
Please, no! %{__cp} hugely decreases readability and if the
situation happens that mkdir and cp are not in the $PATH we will
have much bigger problems than running sed on all .spec files.
I am sorr
On 03/06/2012 03:11 AM, Vijay N. Majagaonkar wrote:
Please, no! %{__cp} hugely decreases readability and if the
situation happens that mkdir and cp are not in the $PATH we will
have much bigger problems than running sed on all .spec files.
I am sorry but this will hit even if you d
> Please, no! %{__cp} hugely decreases readability and if the situation
> happens that mkdir and cp are not in the $PATH we will have much bigger
> problems than running sed on all .spec files.
I am sorry but this will hit even if you don't use macro when tools are not
in $PATH, unless you use fu
>> mkdir -p
>>cp -p ...
It will be good if you make use of macro like %{__cp}
Please, no! %{__cp} hugely decreases readability and if the situation
happens that mkdir and cp are not in the $PATH we will have much bigger
problems than running sed on all .spec files. Use just plain Unix
com
I am not reviewer but I think it make sense following things are good
to incorporate
>># These packages are not require for python >=2.6 but required for python
= 2.5
>>Requires: python >= 2.5
I think your Requires: must be python = 2.5
>>%setup -q -n cloud-%version
is that version shoul
