Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Can I use both the OpenPKG and my vendor RPM at the same time?

openpkg RPM time vendor
0
Posted

Can I use both the OpenPKG and my vendor RPM at the same time?

0

Yes, you can. It might even be necessary, as our RPM tool provides a different set of functionality as the traditional one. Unfortunately, both use the same program name rpm. Pay attention to the program paths when choosing to operate on the OpenPKG repository or a traditional RPM populated one. In any case, do not panic. You cannot accidentally apply the wrong RPM tool, because OpenPKG RPM specifications do not work with other vendors’ implementations. Such other implementations of RPM lack the virtual “OpenPKG” pre-requisite definition (which is provided by the OpenPKG bootstrap package only). Using other vendor RPM specifications with the OpenPKG RPM tool usually works, but stores installation data in the wrong RPM database. This is really the only problem to watch out for. It is good practice to put your vendor rpm tool first in the $PATH, and call the rpm of OpenPKG through an absolute path.

0

[A] Yes, you can. It might even be necessary, as our RPM tool provides a different set of functionality as the traditional one. Unfortunatly, both use the same program name rpm. Pay attention to the program paths when choosing to operate on the OpenPKG repository or a traditional RPM populated one. In any case, do not panic. You cannot accidently apply the wrong RPM tool, because OpenPKG RPM specifications do not work with other vendors’ implementations. Such other implementations of RPM lack the virtual “OpenPKG” pre-requisite definition (which is provided by the OpenPKG bootstrap package only). Using other vendor RPM specifications with the OpenPKG RPM tool usually works, but stores installation data in the wrong RPM database. This is really the only problem to watch out for. It is good practice to put your vendor rpm tool first in the $PATH, and call the rpm of OpenPKG through an absolute path.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.