We manage too many machines, which is made manaable by using up2date.
We push everything as a rpm.
Most "upstream" providers are src rpms, which get a --rebuild and are
deploed to our differnet channels as needed.
But there are some which are CVS type upstream.
We have a program which gives us a revision marker unique to the working
copy, which would allow us to reproduce it each time, it is intended to be
the rpm's release attribute.
A general package would be like so:
Name: package
Version: CVS.Tag
Release: LastModDate.SpecVer
On Thu, 22 Sep 2005, Paul Nasrat wrote:
On Wed, 2005-09-21 at 21:46 -0400, Jason Pyeron wrote:
I am looking for a Frankenstein approach to have rpmbuild -ba SPECFILE
modify its specfile such that the new specfile is the one included in the
srpm.
%prep
# mutate the spec file changing only: release and source0
any suggestions?
Why are you even wanting to get this to work?
The entire point is to have reproducible builds - what actual problem
are you trying to solve? Without understanding that it's hard to
comment/help...
Paul
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Partner & Sr. Manager 7 West 24th Street #100 -
- +1 (443) 921-0381 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you
have received it in error, purge the message from your system and
notify the sender immediately. Any other use of the email by you
is prohibited.
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
