Good Afternoon,
Much obliged!!!!!!!!!!!!!!!!!!
Did anything that I was talking about make any sense?
Let me try to clarify it a little better, I was a little exasperated when writing the post.
I install contrib A that deals with email and has an installation script that installs v2.2 of perl (for this illustration.) After looking around I find contrib B that adds a nice little feature to email that I really want. After downloading it and looking at the rpm's, I determine that it comes with v1.2 of perl. Sometimes contribs.orge with installation scripts and sometimes they don't, either way, do most programs work with newer versions of the dependencies they require? If it comes with an installation script, I've run into a deal with squidguard that installs ACL's but there was something else that I installed before that or the latest release of SME had a newer version of squidguard. Do I remove the lines that deal with the rpm's? I tried that but I don't think it installed properly.
I understand that Linux is a freelance type of OS but are there any standards out there that dictate some of these issues? For example, a standard for installing, uninstalling, compiling, etc. A structure so to speak, do A before B when installing and vica-versa on uninstalling.
I don't claim to know alot about Linux and the internals of the OS but, after working with QS9000 and other similiar standards for manufacturing is skewing my perception of contribs and the likes.
The only example I have that is somewhat in context here is the add-on system that a freelancer developed for IPCOP. It appeared that he had made a structure for contribs and if any author wanted to use his system, they had to meet certain criteria. I like that type of methodology(?) I guess.
A penny for your thoughts, mine get too long sometimes, acckkk...
Wally