Agreed. I'm not arguing, just saying that the typical RPM user isn't someone who is capable of building their own RPMs, yet somehow there is the perception that "RPMs are safe and easy" just because they do a lot of work with just one command and someone says "here's the RPM for product X". There's nothing wrong with a package system, RPM or not, in and of itself, just in the way it's used and in the way it's trusted by default by those who aren't building the packages.
John > -----Original Message----- > From: Jason Pyeron [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 07, 2003 3:41 PM > To: Tomcat Users List > Subject: RE: RPMs [off topic: why rpm?] > > > > IMHO: > > You do have many valid points there. To justifty what we do here: > > We do not assume, the validity of any package (unless our support > contract covers it). That said we role our own RPMs here. > > We put together systems (servers?) for our clients. We need > the assurance > that we can deploy a patch, update, or new software on > these machines. > We use RPMs and MSIs for this reason. > > If you have a hundred RedHat 7.x and fifty Win2k machines out there > running slightly different flavors of your product, you > would use (need?) > this type of mgmt system. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
