M.Hockings wrote:
Why drop the the RHL line if you just turn around and have products like RHPW. RHL became a familiar line, and I think it would have just been better to implement the features of RHPW into RHL and package it as that. (IMO)Bryan Encina wrote:
Personally I find this all very interesting as before reading this thread I didn't even know that there was a spec about where to put things! Here are a few randomish thoughts.
On Windows you will see the typical installer ask to put a new program
at "C:\Program Files\some-vendor-name" but you can change this to
"e:\where-ever-ya-want" and the program will still install. However it
now won't match the documentation -- does this confuse users too? (ans:
yes, even though they chose to put it there)
I don't claim to be an expert on this (or anything at all), but isn't the
reason that Windows can get away with doing this and still having
plugins/addons install correctly because of the registry, one central place
where system wide settings can be looked up? AFAIK there isn't anything
like that in linux (not saying there should be, either) so that's possibly
why installing into non-standard places can make installing/upgrading addons
a little harder.
Yes, this is true, but I have also had to help resolve problems with customers where the registry was corrupt or out of sync due to system failure, user editing, deletion of files without uninstall, etc. Thousands of entries if you use an msi installer. There is a lot to be said for a *simple* ordered way of putting things in the file system (IMHO). That is, I would presume that if a vendor supplies an RPM install then the same vendor should know how to update or remove the install as well.
Mike
Austin
