Le Monday 30 May 2005 15:04, Jos Vos a écrit : > On Mon, May 30, 2005 at 03:37:20PM +0300, Panu Matilainen wrote: > > That's the point I was making: the SRPM can have different requirements > > across architectures if you check it's dependencies for example for > > purposes of installing build dependencies of a given SRPM. So the SRPM > > can have differences based on the arch it was built on, hence the arch of > > an SRPM does have *some* meaning to it. :) > > AFAIK you're wrong here. The src.rpm contains spec file and sources and > dependencies are stored in the spec file, not in the src.rpm metadata. > So the arch does *not* have a meaning... Are you sure ? Build Requirement are propagated into src.rpm as Requirements: [olivier@andromede rpmbook]$ rpm -qp --requires /home/olivier/rpm/SRPMS/name-1-1.src.rpm foo rpmlib(CompressedFileNames) <= 3.0.4-1 Build from: Summary: The summary is short Name: name Version: 1 Release: 1 License: A valid license Group: Group BuildRequires: foo %description The description is multiline Even it's true during build requirement comes from spec parsing.
Attachment:
pgpFUiVN10G2Y.pgp
Description: PGP signature
