On Sat, Aug 19, 2006 at 06:25:30PM -0400, Jack Neely wrote: > There's a fundamental misunderstanding here about using rpm -i. You > claim that it does not function for kmods. Most of us consider your > examples for this an upgrade path rather than an install path. The key point is that neither -U, nor -i, nor any other rpm cli transaction can support kmods. Restricting the starting environment does not count. In this case firefox and any other conventional package can also be installed with -i. So whether you want to give "rpm -i" a name or not, doesn't matter. I call it neither upgarde, nor (co)install, I just make the technical and correct observation that "rpm -i" does not work - as "rpm -U" does not work. And since both do not work rpm cli operation with kmods is impossible which is the final aspect here. Please note that restricting the starting environment (e.g. kmod free setup) does really not count as an argument that rpm -i/-U works. -- Axel.Thimm at ATrpms.net
Attachment:
pgpZjOdXgWbxB.pgp
Description: PGP signature
-- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
