<div dir="ltr"><font face="arial, helvetica, sans-serif">As mentioned in <a href="http://fedoraproject.org/wiki/Packaging:Guidelines#Requires_2">http://fedoraproject.org/wiki/Packaging:Guidelines#Requires_2</a>, <span style="color:rgb(0,0,0);font-size:12.1599998474121px;line-height:18.2399997711182px"> there's no automatic dependency find procedure for </span></font><span style="color:rgb(0,0,0);font-size:12.1599998474121px;line-height:18.2399997711182px"><font face="arial, helvetica, sans-serif">Build requirements</font></span><font face="arial, helvetica, sans-serif"><span style="color:rgb(0,0,0);font-size:12.1599998474121px;line-height:18.2399997711182px">, which means that you must explicitly list stuff that the package requires to build successfully. For requires, the dependency for software running after installation, however, </span><span style="color:rgb(0,0,0);font-size:12.1599998474121px;line-height:18.2399997711182px">There is usually no need to explicitly list.</span></font><div><font face="arial, helvetica, sans-serif"><span style="color:rgb(0,0,0);font-size:12.1599998474121px;line-height:18.2399997711182px">So I defined BuildRequires : python >= 2.6.3 and ignored any Requires in SPEC file, then rpmbuild automatically detected the requires, including rpmlib, libc.so.6, libpython2.7.so.1.0 ...., which would be checked before rpm installation.</span></font></div><div><font face="arial, helvetica, sans-serif"><span style="color:rgb(0,0,0);font-size:12.1599998474121px;line-height:18.2399997711182px"><br></span></font></div><div><font color="#000000" face="arial, helvetica, sans-serif"><span style="font-size:12.1599998474121px;line-height:18.2399997711182px">I prefer to install all packages through rpm under /usr instead of /usr/local, and the following are the files and directories added after installing awscli.</span></font></div><div><div><font color="#000000" face="arial, helvetica, sans-serif"><span style="font-size:12.1599998474121px;line-height:18.2399997711182px">/usr/bin/aws (symbolic link)</span></font></div><div><font color="#000000" face="arial, helvetica, sans-serif"><span style="font-size:12.1599998474121px;line-height:18.2399997711182px">/usr/aws/bin/*</span></font></div><div><span style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:12.1599998474121px;line-height:18.2399997711182px">/usr</span><font color="#000000" face="arial, helvetica, sans-serif"><span style="font-size:12.1599998474121px;line-height:18.2399997711182px">/aws/include/*</span></font></div><div><span style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:12.1599998474121px;line-height:18.2399997711182px">/usr</span><font color="#000000" face="arial, helvetica, sans-serif"><span style="font-size:12.1599998474121px;line-height:18.2399997711182px">/aws/lib/*</span></font></div><div><span style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:12.1599998474121px;line-height:18.2399997711182px">/usr</span><font color="#000000" face="arial, helvetica, sans-serif"><span style="font-size:12.1599998474121px;line-height:18.2399997711182px">/aws/bin</span></font></div><div><span style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:12.1599998474121px;line-height:18.2399997711182px">/usr/</span><font color="#000000" face="arial, helvetica, sans-serif"><span style="font-size:12.1599998474121px;line-height:18.2399997711182px">aws/include</span></font></div><div><span style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:12.1599998474121px;line-height:18.2399997711182px">/usr/</span><font color="#000000" face="arial, helvetica, sans-serif"><span style="font-size:12.1599998474121px;line-height:18.2399997711182px">aws/lib</span></font></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 26, 2015 at 9:54 PM, Jan Schaumann <span dir="ltr"><<a href="mailto:jschauma@stevens.edu" target="_blank">jschauma@stevens.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">hchen29 <<a href="mailto:hchen29@stevens.edu">hchen29@stevens.edu</a>> wrote:<br>
<br>
> As far as I can see, the awscli-1.7.12 do not support make and make<br>
> install commands. It is installed by using python. I don't know how to<br>
> deal with this problem in .spec file, and how to track installed files.<br>
> If I don't know the location of all these files, I cannot write the<br>
> %file part in spec file. How to deal with this problem?<br>
<br>
</span>'make' is just a general purpose utility to execute commands<br>
conditionally based on time stamps. The process to create a package may<br>
default to invoking 'make' (for certain programs), but you should be<br>
able to use a(ny) different command (including none) to build or install<br>
files.<br>
<br>
Identifying the files and their correct location in the file system<br>
hierarchy can be done in a number of ways, and it's up to you to find<br>
one that works for you. (If you do, feel free to share on this list.)<br>
<br>
Remember to identify any dependencies for the package, so that a newly<br>
deployed package will pull in whatever other software may be required.<br>
It seems you already identified 'python' as a dependency here, but there<br>
may be others, including, possibly, some python modules.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Jan<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
cs615asa mailing list<br>
<a href="mailto:cs615asa@lists.stevens.edu">cs615asa@lists.stevens.edu</a><br>
<a href="https://lists.stevens.edu/mailman/listinfo/cs615asa" target="_blank">https://lists.stevens.edu/mailman/listinfo/cs615asa</a><br>
</div></div></blockquote></div><br></div>