<div dir="ltr">Thank you for the corrections you have suggested. It is not a delta rpm in the true sense. (long email please brace)<div><br></div><div style>Let me see if my approach is right or not. Please do critique my approach, if any.</div>
<div style><br></div><div style>We have had to customize the Apache tomcat by adding some extra folders to the apache tomcat.</div><div style><br></div><div style>We also have had to modify a few of the properties files, .sh files etc., of the vanilla version.</div>
<div style><br></div><div style>What I have done is, before customization, made an rpm of the vanilla version.(apache-tomcat-vanilla-7.0.37.rpm)</div><div style><br></div><div style>I have then started the process of creation of a .rpm of the differences aka the extra folders, modified props, modified .sh files etc.,(name is apache-tomcat-differences-7.0.37.rpm)</div>
<div style><br></div><div style>I will put Requires for the apache-tomcat-differences-7.0.37.rpm as apache-tomcat-vanilla-7.0.37.rpm and Conflicts as apache-tomcat-differences-7.0.37.rpm</div><div style><br></div><div style>
I wont do deltas of deltas. The idea is to install base and superimpose the extras/mods.</div><div style><br></div><div style>Now that i have hopefully have clarified that</div><div style><br></div><div style><div style="font-family:arial,sans-serif;font-size:13px">
What I would like to do is</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">a. check if apache-tomcat-7.0.37-vanilla is installed (this I can do in the Requires section of the preamble, I presume the name is the name of the rpm package)</div>
<div style="font-family:arial,sans-serif;font-size:13px">b. enquire the rpm tool as to where the package apache-tomcat-7.0.37-vanilla is installed ? not sure how to do this.</div><div style="font-family:arial,sans-serif;font-size:13px">
c. cd to the location the apache-tomcat-7.0.37-vanilla is installed and backup a few files.</div><div style="font-family:arial,sans-serif;font-size:13px">d. then do a cp -r from the BUILD folder to the target folder.</div>
<div><br></div><div><br></div><div style>Kindly read this long email and help.</div><div style><br></div><div style>-Narahari</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 4, 2013 at 8:17 PM, Scott McBrien <span dir="ltr"><<a href="mailto:smcbrien@gmail.com" target="_blank">smcbrien@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>I would attempt to dissuade you from using a delta rpm. With deltas, you end up being really really concerned with versions. So after your first delta gets applied, if you have another update, you make a delta of the delta, which means if there's a machine with the vanilla rpm out there and you apply delta2 on it, things devolve into madness quite quickly. Does a regular RPM contain more stuff and take up more space? Sure. But if an RPM is 10MB or 100MB, who really cares. The simpler you keep your packages, the more independent you keep your packages the less likely that you get into a situation you can't, or is extremely difficult, to reverse.</div>
<div><br></div><div>If you choose to ignore my advice, you should use not only the package name, but also the version in your Requires for your drpm, that should keep you from applying a drpm to a box that is not at the appropriate version to accept the delta successfully.</div>
<div><br></div><div>But seriously, keep it simple, it will improve your life in the long run, and admins who follow you will praise your good works rather than spitting and cursing at the mention of your name.</div><span class="HOEnZb"><font color="#888888"><div>
<br></div><div>-Scott</div></font></span><div><div class="h5"><div><br>On Jun 4, 2013, at 7:23 PM, "Narahari 'n' Savitha" <<a href="mailto:savithari@gmail.com" target="_blank">savithari@gmail.com</a>> wrote:<br>
<br></div><blockquote type="cite"><div><div dir="ltr">I built my vanilla Tomcat rpm and the %install section has<div><br></div><div><div>mkdir -p $RPM_BUILD_ROOT/opt/</div><div>cp -R /home/virtual/rpmbuild/BUILD/apache-tomcat-7.0.37 $RPM_BUILD_ROOT/opt</div>
</div>
<div><br></div><div>I also built the delta.rpm and I am in the process of tinkering the %install section for that.</div><div>What I would like to do is</div><div><br></div><div>a. check if apache-tomcat-7.0.37-vanilla is installed (this I can do in the Requires section of the preamble, I presume the name is the name of the rpm package)</div>
<div>b. enquire the rpm tool as to where the package apache-tomcat-7.0.37-vanilla is installed ? not sure how to do this.</div><div>c. cd to the location the apache-tomcat-7.0.37-vanilla is installed and backup a few files.</div>
<div>d. then do a cp -r from the BUILD folder to the target folder.</div><div><br></div><div>Where should I put the code for all this ? I presume the %install section ?</div><div>What all heavy lifting can I or should I do in the %install section and is using macros a requirement or a good thing to do kind of a thing ?</div>
<div><br></div><div>Kindly help.</div><div><br></div><div>-Narahari</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 3, 2013 at 3:31 PM, Scott Plante <span dir="ltr"><<a href="mailto:splante@insightsys.com" target="_blank">splante@insightsys.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:12pt;font-family:arial,helvetica,sans-serif"><div>"<span style="font-family:Helvetica,Arial,sans-serif">Also, tomcat is not really built as in gcc or cc or whatever aka no make or configure."</span><div>
<br></div></div><div>Mostly true, however there is an optional native part, found in the "[tomcat-root]/bin/commons-daemon-native.tar.gz" file. If you're creating a Tomcat binary RPM it would be a good idea to compile this, as it allows you to have Tomcat listen on port 80/443 (or a port <1024) directly without running Tomcat as root. You don't need this if you're running Tomcat behind Apache HTTP, but for example WebRTC won't work proxying through ajp.</div>
<div><br></div><div>Scott<br><hr><div style="font-size:12pt;font-style:normal;font-family:Helvetica,Arial,sans-serif;text-decoration:none;font-weight:normal"><b>From: </b>"Narahari 'n' Savitha" <<a href="mailto:savithari@gmail.com" target="_blank">savithari@gmail.com</a>><br>
<b>To: </b>"Atlanta Linux Enthusiasts - Yes! We run Linux!" <<a href="mailto:ale@ale.org" target="_blank">ale@ale.org</a>><br><b>Sent: </b>Sunday, June 2, 2013 10:02:11 PM<br><b>Subject: </b>[ale] rpm's src vs binary and the confusion<div>
<div><br><br><div dir="ltr"><div><div><div><div><div><div><div><div><div>Friends:<br><br></div>I am building an rpm for Apache Tomcat version 7.0.37.<br><br></div>Sorry to ask a lame question but what is the diff between src rpm and regular rpm ?<br>
</div>(dont flame, I know I have read it but it confuses me when I am building)<br><br></div>Also, tomcat is not really built as in gcc or cc or whatever aka no make or configure.<br><br></div>So in the install section what should I be really doing ?<br>
</div>Spec file is here.<br><br><a href="http://pastebin.com/f6P64tSQ" target="_blank">http://pastebin.com/f6P64tSQ</a><br><br></div>Also, if I have a custom name for the rpm I am building, what macros or env variables are available in the %install section ?<br>
<br></div>Regards,<br></div>-Narahari<br><div><div><div><br></div></div></div></div>
<br></div></div><div>_______________________________________________<br>Ale mailing list<br><a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br><a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br><a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br></div></div><br></div></div></div><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Ale mailing list</span><br><span><a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a></span><br>
<span><a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a></span><br><span>See JOBS, ANNOUNCE and SCHOOLS lists at</span><br><span><a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a></span><br>
</div></blockquote></div></div></div><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div><br></div>