Reaching the architecture review stage of my little project and rpm and yum are still on the table. I decided to review this small thread and came across "if the os is managed by rpm all of the above are possible." I may be mis-reading this but why would the OS have to be managed by rpm to make the 'above' (now below) possible? I have whittled and hammered down to red hat only OS support, for now, and rpm and yum are being used on the target systems but I don't understand why the OS would have to be managed by rpm to use rpm to transport other data. Thanks -----Original Message----- From: yum-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:yum-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of seth vidal Sent: Monday, April 09, 2007 4:11 PM To: Yellowdog Updater, Modified Subject: RE: Using YUM to manage S/W distros other than linux On Mon, 2007-04-09 at 15:06 -0700, Gallie, Keith wrote: > sv> what did you have in mind? > > multi-site s/w release management; s/w meaning anything a developer > releases, perl, compiled exes, compiled libraries, documentation, etc. if the os is managed by rpm all of the above are possible. -sv _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum
