PDA

View Full Version : How does Arch have low quality packages?



eljoeb
February 16th, 2008, 07:32 PM
I saw someone comment a couple of times that Arch has poor quality packages. What does this mean? I swear I remember reading somewhere that Arch used the most vanilla packages with nearly no distro specific packaging. Why are these packages of low quality?

PurposeOfReason
February 16th, 2008, 07:33 PM
Can you post where you read this. Arch has the newest packages available and can even be so new to being unstable if you'd like.

fwojciec
February 16th, 2008, 08:05 PM
I saw someone comment a couple of times that Arch has poor quality packages. What does this mean? I swear I remember reading somewhere that Arch used the most vanilla packages with nearly no distro specific packaging. Why are these packages of low quality?

There are always people out there who are all too happy to pass damning judgments on things they don't really know or understand well enough to judge.

eljoeb
February 16th, 2008, 11:16 PM
Hmmm... not sure. I've been using Arch for almost a year now, and am pretty happy with it. I saw the comment and couldn't figure out why. However, I couldn't find it again, so I'm taking this as a sign from the internet gods that I need to stop posting in the forums of a distro I don't use. Either that or I'm drinking too early again.

bwtranch
February 16th, 2008, 11:18 PM
There are always people out there who are all too happy to pass damning judgments on things they don't really know or understand well enough to judge.
That's really true fwo. Another thing I would like to point out is that the package is only as good as the source code, anyway. Look at Windows if you don't believe it.

K.Mandla
February 17th, 2008, 12:19 AM
I saw someone comment a couple of times that Arch has poor quality packages. What does this mean? I swear I remember reading somewhere that Arch used the most vanilla packages with nearly no distro specific packaging. Why are these packages of low quality?
This is the first time I've heard of this, and frankly it sounds a little FUDdy. (Is that a word? :) )

b9anders
February 18th, 2008, 10:52 AM
first I've heard of it.

The only bad package experience I've had with Arch was Exaile which had trouble deciphering some characters in the tags of my music collection and consequently refused to import any of it.

It was ridiculously easy to grab a PKGBUILD and compile the latest version from source to correct it though. Imo, the package management and the ease with which one can install from source for what isn't in the repositories is one of Arch's greatest strengths.

Crooksey
February 18th, 2008, 08:19 PM
Probably someone complaing about the fact that they are unpatched and vanilla.

Some people prefer patched packages, opposed to vanilla.

Tristam Green
February 18th, 2008, 08:26 PM
This is the first time I've heard of this, and frankly it sounds a little FUDdy. (Is that a word? :) )

Could re-coin "FUDdyduddy!"

+1

mivo
February 18th, 2008, 11:14 PM
If people start to spread FUD about Arch, the distro is obviously becoming popular and mainstream! ;)

RedSquirrel
February 18th, 2008, 11:37 PM
I think the package quality of Arch is high, e.g., the Arch devs dealt with that kernel bug very quickly.

Incidentally, firefox is one package that is patched. That is the reason it's called "Bon Echo". ;)

yabbadabbadont
February 18th, 2008, 11:43 PM
I just wish that all the packages were updated as quickly for security issues. Mplayer is still vulnerable and the patches to fix it were released almost a month ago. Granted, it isn't a critical part of the system, but given its popularity, and the fact that it is in Extra, I would think that it would have been updated by now. (I even bumped the bug by adding direct links to the patches that Mplayerhq released) Which reminds me, I need to pull down the PKGBUILD and rebuild it myself with those patches...

RedSquirrel
February 19th, 2008, 02:52 AM
I just wish that all the packages were updated as quickly for security issues. Mplayer is still vulnerable and the patches to fix it were released almost a month ago. Granted, it isn't a critical part of the system, but given its popularity, and the fact that it is in Extra, I would think that it would have been updated by now. (I even bumped the bug by adding direct links to the patches that Mplayerhq released) Which reminds me, I need to pull down the PKGBUILD and rebuild it myself with those patches...
Good point. A month is a long time. I wonder how many packages are in that state...

yabbadabbadont
February 19th, 2008, 03:07 AM
Good point. A month is a long time. I wonder how many packages are in that state...

Not only that, but the PKGBUILD in the official cvs for mplayer won't build due to an invalid URL in the source array. It was easily fixed, but it made me wonder about the quaility of the tree. I poked around a bit in the tree and decided that I would rather put gentoo back on my machine. I'm booted on the liveDVD now. (which is why I've been a bit slow in the games threads ;))

PurposeOfReason
February 19th, 2008, 03:08 AM
I just got my first complaint when mpd was updated but a dependicy was forgotten. It was fixed quickly though.

yabbadabbadont
February 19th, 2008, 03:10 AM
@RedSquirrel: Hey, if you stay on Arch, would you mind testing a PKGBUILD for me now and then. I have a package in the AUR that I maintain. "ca-certificates" It tracks the Debian (and Ubuntu and Gentoo) package by the same name, and hasn't been updated by them since early last year, so I doubt that I would need to bug you anytime soon.

RedSquirrel
February 19th, 2008, 03:35 AM
Sure, no problem.

yabbadabbadont
February 19th, 2008, 03:50 AM
Sure, no problem.

Thank you. I'm going offline for a while. I have to rebuild gcc and python, and then build xorg and fluxbox. Have fun in the word games without me. :D