-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nope, no SRPM. The product gets compiled outside of the RPM build process -- we just use RPM as a packaging/delivery vector. So the spec file largely consists of an %install section that specifies where to copy the files from, and a %file section listing which files are owned by the RPM. Stanley, Jon wrote: > If you install the SRPM (just like an RPM), the spec file will be in > /usr/src/redhat/SPECS. Is that what you want? Or do you not have the > SRPM? > >> -----Original Message----- >> From: rpm-list-bounces@xxxxxxxxxx >> [mailto:rpm-list-bounces@xxxxxxxxxx] On Behalf Of Marcin >> Krzysztof Porwit >> Sent: Wednesday, August 30, 2006 2:41 PM >> To: RPM Package Manager >> Subject: generating a spec file from an RPM? >> > Are there any tools or means out there to reverse-engineer a spec file >>>from an existing RPM? We currently build rpm packages using install4j, > but we find ourselves needing to do a small one-off > modification that is > outside of install4j's abilities... > -- > Marcin Krzysztof Porwit > mporwit@xxxxxxxxxxxx > > #include <stddisclaimer.h> >> _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list >> - -- Marcin Krzysztof Porwit mporwit@xxxxxxxxxxxx #include <stddisclaimer.h> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE9d0W4OZU6cX5VBERAraNAJ9xAz0hDi1llhqnBMK8q7HeXyl0GACfY9dn dLH2poP1ATjugV4jlhIJ4A0= =kH4n -----END PGP SIGNATURE----- _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
