Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In English: it's a system to keep track of changes made to code when there are multiple people working on the same project.
When you download a cvs package from a CVS server, you are downloading the absolute latest version of the software. And by that, I mean you are typically getting code that was merged into the project that day. The project is being actively developed, and you're downloading a daily snapshot.
This is great if you want to stay on the bleeding edge. It's not so great if you want stability. Someone may have just merged in code that has a bug. Someone may have checked in code that prevents a successful compile. If the developers have a strict checkin policy, then that lowers the chances, but people are human and sometimes make mistakes.
However, some projects will create "releases" inside CVS that you can check out. These are considered stable because the set of files won't change; they're frozen. With this route, you obviously aren't getting the latest-and-greatest.
My suggestion: unless you're a developer with the project, then you probably shouldn't mess with CVS unless it's the only way the project team offers the code (free Cedega is an example), or at least, stick to stable releases.
i hae used that to get the latest packages
if u want to get the latest develpment packages ,and cannot wait for their Stable release then u can do that by CVS, if it is supported
the disadv. will be that they are not tested for stabilty so might end up with some bugs
CVS == Concurrent Versioning System - a source code management system.
CVS is where programmers check in their latest code revisions. The code is the latest and (hopefully) greatest, but at best it can be considered beta. It is often pre-alpha. It depends on the check-in standards and maturity of the project.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.