AutoReqProv or AutoReq/AutoProv?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi.
My issue is this: an rpm is created in a dev. environment, where all of
its dependencies are fulfilled, yet is installed in such environments
where those deps are only partially fulfilled. In order to alleviate the
dep clash during installation, the maintainer builds the rpm with
"AutoReqProv=no". Yet this causes the RPM not to auto-generate any
"Provides" clauses. Packages depending on this rpm fail installing
because of this.
 
If I understand correctly, AutoReqProv parameter triggers
auto-generation of both "Requires" and "Provides". I've found several
indications that there used to be an 'AutoReq' and an 'AutoProv',
separating this functionality, but it seems those params are not
supported any more.
a) is this correct - that 'AutoReq' and 'AutoProv' are obsolete?
b) Other than manually specifying "Provides" in the spec file, is there
a different suggested method of handling such a case?
c) What's the reason, technically, to bundle 'AutoReq' and 'AutoProv'
together? Can't they be separated?
 
10x,
Amit

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux