fedpkg prep

Jesse Keating jkeating at redhat.com
Wed Sep 1 00:26:22 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/31/10 5:16 PM, Steve Dickson wrote:
> I guess I don't understand why all this state is needed to simply
> lay down the tar ball and apply the current patches... The tar ball
> and patches have nothing to do with the version of Fedora or 
> the state of a repo... To me, it seems like such a simple process 
> that state or objects or whatever should not be needed... 

Because packages function differently (including what patches to apply)
depending on Fedora / RHEL versions, etc..  These are discovered by
reading the macros which may be in the spec files.  Therefor we need to
have those defined properly before we call rpm (the Makefile system did
this too).

The difference between the Make system and fedpkg is that the Make
system relied upon the name of the directory you happened to be in, and
a file in ../common/ that translated the directory name and figured out
rpm defines.  Since local clones can be in any directory you want,
fedpkg cannot rely upon this.  We need to know what remote branch your
clone is tracking in order to determine what fedora you are targeting.
That's why your git repo has to be in a healthy state.

- -- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkx9nasACgkQ4v2HLvE71NVg7wCfWU/Mk5t/ExabTAkQzil23FA0
r+oAoLHXLjiyhS9QP5iiQdGXoq9+EjDi
=Obiz
-----END PGP SIGNATURE-----


More information about the devel mailing list