Hi, I want to build a single RPM that has more than one software in it and a different name from them. Let's imagine for the sake of example that i want to make an RPM called databases.rpm that installs both MySQL and Postgres. How can i do this with a single spec file ? I've googled for an hour or two and found no info about this issue. Can someone enlighten me, please ? WarmRegards, M?rio Gamito -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070302/20b9d81e/attachment-0001.html>
2007/3/2, M?rio Gamito :> > Hi, > > I want to build a single RPM that has more than one software in it and a > different name from them. > > Let's imagine for the sake of example that i want to make an RPM called > databases.rpm that installs both MySQL and Postgres. > > How can i do this with a single spec file ? > > I've googled for an hour or two and found no info about this issue. > > Can someone enlighten me, please ? >Hello, The best way to do that is to create an empty RPM that depends on Mysql and Postgres. Of course using that method you will have to provide more than one rpm .. -- Virtue is its own punishment. - Aneurin Bevan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070302/29017ac2/attachment-0001.html>
M?rio Gamito wrote:> Hi, > > I want to build a single RPM that has more than one software in it and a > different name from them. > > Let's imagine for the sake of example that i want to make an RPM called > databases.rpm that installs both MySQL and Postgres. > > How can i do this with a single spec file ?Requires: package1 Requires: package2 ...
Maybe Matching Threads
- How to refer to my package from another package DESCRIPTION
- Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
- Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
- Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
- problem with a repo