I should add, in a properly deployed rpm system, deploying (downloading/installing), configuring and running are three completely separate steps that do not imply one another. (deploying and updating OTOH are quite similar) It is a very powerful model that renders many complex operations easy to handle. However, it is also completely confusing to people that come from systems with less advanced facilities, that are used to compensate the management limitations with complex scripted or manual operation that mix all phases in random order. Learn to separate the steps in your design, you'll soon find out it makes a lot of things simpler and rpm/dnf can take care transparently of many things that used to be manual. Trying to impose a workflow that is contrary to rpm/dnf basic design usually ends badly. Not that rpm/dnf is not flexible enough to do it but it usually works a lot worse than using them as they are intended to be used (as all the people that try to replicate windows installers scripts rediscover every year). -- Nicolas Mailhot _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
