<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><div>Thanks for the advice - that's an angle I hadn't considered. Should work just fine.</div><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Stuart D. Gathman <stuart@bmsi.com><br><b><span style="font-weight: bold;">To:</span></b> General discussion about the RPM package manager <rpm-list@lists.rpm.org><br><b><span style="font-weight: bold;">Sent:</span></b> Tue, February 22, 2011 10:56:40 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: Bypassing source checks in rpmbuild -bc<br></font><br>
On Tue, 22 Feb 2011, Maule Mark wrote:<br><br>> We are using a hybrid development process in our company where we take an<br>> srpm, run it through rpmbuild -bp and then check the prepped source (ie.<br>> BUILD/<pkg>) and spec file into our source control system. We then do<br>> development against the expanded source and will periodically use our source<br>> control system to generate a patch from accumulated changes and regenerate<br>> the srpm.<br>> <br>> We throw away the SOURCES directory after expanding to save checking in some<br>> duplication.<br>> <br>> To compile things for testing/develoopment, we then want to just be able to<br>> use rpmbuild -bc -short-circuit ...<br><br>We use a makefile to generate the SOURCES from cvs. You can do something<br>similar:<br><br>cvstar: $(SRCTAR)<br><br>$(SRCTAR):<br> cvs export
-r$(CVSTAG) -d $(PKG) java/bmsi/db<br> tar cvf $(PKG).tar $(PKG)<br> gzip -f $(PKG).tar<br> rm -r $(PKG)<br><br>Add your own rule to move the source tarball to the SOURCES directory.<br><br>> Is there any way to bypass thyis check? I realize this isn't standard<br>> practice - but it's the method we'd like to use if possible.<br><br>Generating the SOURCES from your source control system is easily automated,<br>as above. The SOURCES check verifies that the sources actually *can* be<br>generated from your source control system. It is not a check that you<br>want to bypass.<br><br>-- <br> Stuart D. Gathman <<a ymailto="mailto:stuart@bmsi.com" href="mailto:stuart@bmsi.com">stuart@bmsi.com</a>><br> Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154<br>"Confutatis maledictis, flammis acribus
addictis" - background song for<br>a Microsoft sponsored "Where do you want to go from here?" commercial.<br>_______________________________________________<br>Rpm-list mailing list<br><a ymailto="mailto:Rpm-list@lists.rpm.org" href="mailto:Rpm-list@lists.rpm.org">Rpm-list@lists.rpm.org</a><br><span><a target="_blank" href="http://lists.rpm.org/mailman/listinfo/rpm-list">http://lists.rpm.org/mailman/listinfo/rpm-list</a></span><br></div></div><div style="position:fixed"></div>
</div><br>
</body></html>