On Tue, Apr 17, 2007 at 04:57:47PM +0100, Steven Maddox (Architect) wrote: > Hi folks, > > Angry mob here (if I was more than one person)... It's very nice of you > to lecture me on what is LAMP and all the different packages that theres > are - but I already 'get' all of that! > > What I am after is recommendations on how to go about it, someone did > post a tutorial which was nice - however it is from the pespective of > installing Debian a fresh, which I can't use! > > Also very little of you seem to have seen that I was after > recommendations for open source control panels too... I have however > made a short list of them here. > > VishwaKarma - http://kandalaya.org/vishwakarma.shtml > Webmin - http://www.webmin.com > H-Sphere - http://www.psoft.net > SysCP - http://www.syscp.org > AlternC - http://www.alternc.org > Web-cp - http://www.web-cp.net > Ravencore - http://www.ravencore.com > ISPConfig - http://sourceforge.net/projects/ispconfig > DTC - http://www.gplhost.com/software-dtc.html > ZPanel - http://www.thezpanel.com > ASM : http://www.acctmgr.com > > Of course if any of these are in the debian repo's then I would assume > they also have dependencies attached insuring all the extra packages > they need (like the LAMP related packages) are installed too... which > would be handy. > > Thoughts! >
Debian package names are very similar to the given name of a piece of software, but upper case letters and punctuation are avoided in package names. I like to use the given name and the word 'Debian' as search criteria in Google to find information as to whether or not a piece of software has been packaged for Debian. Try it. I have found it to be a very quick way to get at the final, correct answer, which is usually found down inside the software's web site, or somewhere inside www.debian.org. Dependencies are handled automatically by the Debian apt packaging system, if the package has been properly built. Packages that don't handle dependencies are not supposed to be allowed into Debian repositories. But mistakes can happen. If some package won't install for any reason, that is a reportable bug against the package. A Debian package is much, much more than a tarball. Debian is very picky about copyrights and licenses. Some software may have been packaged for Debian, but is not available in the Debian 'main' repository because its license is not sufficiently 'free' to satisfy Debian standards, or it depends on other software that is not sufficiently 'free'. Software that has licensing 'complications' is often made available in the 'contrib' and 'non-free' repositories. These distinctions matter to me, and I like Debian for making them. I don't want to become dependent on a piece of software that I then discover I have no legal right to use. HTH -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
