You are not logged in.
- Topics: Active | Unanswered
#1 2006-08-01 22:29:48
- GhostRider
- Member
- Registered: 2006-08-01
- Posts: 12
Pacman Repositories,"Current" Vs "Testing
Hi,
I'm trying to figure out the differences between "current" and "testing" repositories...
as the arch authors claim that there is no official "stable" release,
i'm trying to understand what stands behind this arrengement.
common sense says that "current" is actually "testing", but,
if that's the case, how come that there are two reopsitories
for the same target?
btw,
sorry for my bad english. 
Thanks,
GhostRider 8)
Offline
#2 2006-08-01 23:18:51
- Gullible Jones
- Member
- Registered: 2004-12-29
- Posts: 4,863
Re: Pacman Repositories,"Current" Vs "Testing
Current is for up-to-date software that has been tested and proven stable. Testing is for making sure that stuff works. A system using the Testing repo is generally stable enough for desktop use if managed correctly, but I wouldn't use Testing on a server.
(Note that, if you use Testing, you must also have the Current repo enabled.)
Offline
#3 2006-08-02 19:48:36
- phrakture
- Arch Overlord
- From: behind you
- Registered: 2003-10-29
- Posts: 7,879
- Website
Re: Pacman Repositories,"Current" Vs "Testing
Generally, testing has stuff in it that the maintainer feels may break systems... for instance, there are new mkinitcpio and klibc packages in testing at the moment. They "work for me", but i don't want them put into current because they may cause a system to be unbootable.
Offline