Re: Scripting language dependencies

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

 



On 02/17/2012 09:16 AM, Bill Nottingham wrote:
> Jon Masters (jcm@xxxxxxxxxx) said: 
>> I hope everyone is having a good day. Here in the Fedora ARM project,
>> we're having a great time overall, but we've run up against a familiar
>> foe in our preparation for Fedora 17 and rawhide: superfluous deps in
>> SPEC files. Today's example is a shell-escaped call to Ruby just to
>> determine some gcc flags for an unrelated package build, but that's just
>> today's example. There are many others, so some standard would help.
> 
> OK, so how about:
> 
> ...
> Scripting inside of spec files
> 
> Inside of a spec file, sometimes it is necessary to call a programming or
> scripting language during %setup, %build, or %install. In Fedora, spec
> files may in general only use the following languages for this purpose:
> 
> 1. Python
> 2. Perl
> 3. awk/sed
> 
> Also, if your package already BuildRequires a specific scripting language
> (such as Ruby, or Tcl) as part of its normal compile process, it may also be
> called from the spec file.

Following up, I like the suggestion you made and I wonder what the next
step would be?

Jon.


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



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

  Powered by Linux