Linked by Ben Mazer on Wed 15th Oct 2003 20:58 UTC
A few months ago I was a Slackware Junkie. I loved it, and laughed at those who used 'more automatic' distributions (ok, I didn't actually laugh). Then Arch Linux 0.5 came out and I was very intrigued by it. I was getting tired of having to compile updated packages myself. 
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Alot of people are bringing up a security concern with the packages and the 'incoming' ftp site. This comes from not knowing how makepkg works. Inside all those packages on the 'incoming' ftp site there is a PKGBUILD file. This PKGBUILD file contains all the information to build that package using the "makepkg" command. This file is very easy to read and understand as the bulk of it is just declarations and bash scripts. Most importantly the PKGBUILD file contains a link to the source files from the publisher. Makepkg will download the "official" files and create the package from those files. By creating packages off of the PKGBUILD you eliminate the contributor as a security risk.