effective difference between "Requires:" and "PreReq:"?

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

 



  i just want to clarify the difference between the "Requires" and "PreReq"
directives in a spec file.

  from johnson's book, i read that "In most usage, a PreReq: acts just like
a Requires:...".  the stated difference is that PreReq: exists only to allow
for a manual order to dependencies.  but what is the technical difference?

  in both cases, if a listed dependency is already on the system, then you're
good to go, so there's no difference there.  so the only difference could be
if you're trying to install two packages with some kind of dependency 
relationship, in the same command.

  imagine package A, which has a PreReq: or Requires: directive listing 
package B, neither of which is on the host at the moment.  is it legal in
either case to do 

  # rpm -i A.rpm B.rpm

if A "Requires" B, is the above legal?  and does this differ if A lists B as
a PreReq?  and, in either case, if the operation is legal, is B forced to be
installed first?  or only in the case of B being a PreReq?  or is it arbitrary?

pedantically yours,
rday



_______________________________________________
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