| Re: yum.repo per VE [message #21918 is a reply to message #21736] |
Wed, 17 October 2007 22:02   |
 |
dowdle
Messages: 261
Registered: December 2005
Location: Bozeman, Montana
|
Senior Member |
|
|
| ntenev wrote on Mon, 15 October 2007 09:07 |
1) yum (inside VE) detect all packages, including that are installed on HN and upgrade them all (locally for VE). It's not big problem, VE still works fine, but I search a little more "clean" solution.
|
What? If your VPS needs updates, you should do them... rather than just using yum to install new packges only. You do have the overhead of having yum, it's deps, and the database it maintains... but if you do a "yum clean all" after you do package installs, it frees up a bit of disk space.
| Quote: |
2) vzyum is perfect "central" solution. If I install yum inside VE then it will be "second tool for separate case" wich is something that I wish to not use at this time.
|
An ugly way to achieve this, I think... would be to make a separate yum config for each scenerio... put it where it needs to go and then tack on .scenerioname to the end of it... which scenerioname being some arbitrary word that helps you identify which file is for which usage case. When working in scenerio one, copy the whatever.repo.scenerio1 to whatever.repo and do your work. So basically you are have one config file that applies to all of them but you keep change it depending on which VPS you are working with at the time.
--
TYL, Scott Dowdle
Belgrade, Montana, USA
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
