Re: IDS 2000 SOFTWARE
Colonel Panic wrote: > > In article <382BACBA.C181D5AF@bellsouth.net>, > Tim Schaefer <tschaefe@bellsouth.net> wrote: > >The fact that a program exists is not an excuse to use it. CPIO is the wrong media plain > >and simple for software distribution. It is not in mainstream use, especially in LinuxLand, > > Have you honestly never heard of .rpm files? Are you completely unaware > that RPMs are implemented internally as cpio and can easily be converted > to plain cpio files? > Yes, I am completely unaware of how RPM works, nor do I care, nor do I want to know how it works. As far as I'm concerned I would like to see it completely disappear from the face of the earth. Why go through this pointless extra step? The option list for RPM reads like spaghetti, not to mention that half the options don't work as advertised, and you must hack endlessly to make it work. For you it's easy, make the mess, then let the customer deal with it. In my estimation it's sloppy, shoddy work to say the least, and a total disregard for the customer. Not to mention arrogance. But this is Informix-as-usual, let the customer be damned. > This is *exactly* why IDS.2000 was shipped as cpio, and why IIF.2000 > (following shortly after) will ship as RPM. (IDS.2000 would have also > shipped as RPM, but it had to enter finalQA before the new, one-step > RPM install was approved... since IIF.2000 was following so soon after, > they chose cpio for now.) > You people are lost. > And for those who dislike RPM: you can just convert the .rpm file into > a cpio file and then perform a traditional UNIX-like install using > that cpio file, using the standard "rpm2cpio" utility. (And if your > distro lacks it, you can download an up-to-date version of rpm > and rpm2cpio from www.rpm.org). This is all addressed in an article > on the subject on the Tips and Techniques page of the Linux Corner > of the Informix web site. > Uh huh... <drool forming> How bout just simply releasing a gzipped tar file and saving all these stupid steps? Is this too much to ask? No, that would be too simple, too much in favor of mainstream thinking and certainly would favor the customer, being simpler and easier to deal with. But hey, you and your company know best, what with the stellar stock performance, great reviews in all the trade rags, great marketing programs, and gosh, market share that compares to none. You're the great Informix, you know best. > And the RPM versions for IIF.2000 and 2.4 ClientSDK/Connect will now > be one-step installs, where all the prompts for serial/key/directories/ > role-separation/etc. will be processed within the rpm command itself -- > no need to run a separate script after the fact... > GAwd. What about allowing me the installer the options I want? RPM is simply a mess, and extra trouble. But of course you don't give a rat's ass about the customer, so it doesn't matter to you. Have you ever considered that maybe the installation *I* want to do is different than what the RPM wants to do? And that I may not want to learn RPM or have anything to do with it???? BTW, are you going to RPM on other UNIXes? Sheesh. > >Nope, in the course of my days and weeks day in and day out of whatever it is that I do, > >I never EVER use CPIO. > > If you "never EVER use cpio", then you never ever use RPMs, which means > that you never ever use any version of Linux on which IDS or IIF has > been certified... so the issue seems moot. [-: > I use SuSE. I do not, will not use RedHat until it is cleaned up and more professional. And even if I do decide to use RedHat, I should not be forced to use those goddam RPM files. As far as using RPMs, it is a part of installation for many programs, but in my estimation is not appropriate for IDS when there are certain installations that are not "default". Such as having multiple installations on one machine. How do you address that with RPMs? You and the others seem to have this hell-bent need to overcomplicate the process, and I hope it will accelerate your downfall. As usual let your arrogance be your guide. My interest is in simplicity, yours is in simply being Alan. Tim > -- > Alan Denney yosemite at accesscom.com -- . .- .-- .--- .---- Tim Schaefer .----- tschaefe@bellsouth.net .---- http://www.inxutil.com .--- http://www.datad.com .-- .- .
In article <382C636E.13AA480A@bellsouth.net>, Tim Schaefer <tschaefe@bellsouth.net> writes >Colonel Panic wrote: >> >> In article <382BACBA.C181D5AF@bellsouth.net>, >> Tim Schaefer <tschaefe@bellsouth.net> wrote: >> >The fact that a program exists is not an excuse to use it. CPIO is the wrong >media plain >> >and simple for software distribution. It is not in mainstream use, >especially in LinuxLand, >> >> Have you honestly never heard of .rpm files? Are you completely unaware >> that RPMs are implemented internally as cpio and can easily be converted >> to plain cpio files? >> >Yes, I am completely unaware of how RPM works, nor do I care, nor do I >want to know how it works. As far as I'm concerned I would like to >see it completely disappear from the face of the earth. > >Why go through this pointless extra step? The option list for RPM Informix supply their product using the most common format for that OS. On Linux RPM is the standard. Invented by Redhat even other distributions use or support RPM! Simple! -- David Williams