You are not logged in.
Pages: 1
I've always been a little confused about the CVS. What is it? How does it work? How would one use it?
Thanks!
Offline
Offline
"code revision management tool" came to my mind atm,
subversion is the improved(some are different but mostly very convenient) implementation(fork) of cvs.
BTW, git also very interesting tool same kind of..
I removed my sig, cause i select the flag, the flag often the target of enemy.
SAR brain-tumor
[img]http://img91.imageshack.us/img91/460/cellphonethumb0ff.jpg[/img]
Offline
Offline
Ahhh ... had a feeling about that So in the AUR, it's probably best to get the CVS versions of things because it's always up to date, right?
Offline
Ahhh ... had a feeling about that So in the AUR, it's probably best to get the CVS versions of things because it's always up to date, right?
Yes and no. CVS is the current development code. It's the most up to date, but unlike a regular release there's no guarantee it will be stable. Essentially getting the CVS (or SVN, which is the same sort of thing) version of a package means you're trading some (potential) loss of stability for the latest and greatest features.
Jarsto
Offline
maybe i'm just being nit-picky here, but getting the CVS or SVN package from AUR doesn't guarantee you have the latest code either. Generally, the PKGBUILD will specify a revision number to get. CVS and SVN allow you to not only get the latest code, but also to backtrack, get older code, and see the differences.
SO, in order for you to get the LATEST code, you either have to edit the PKGBUILD to get the last revision, or wait for an update on the AUR.
Beware though that not all CVS revisions are safe. A coder can commit a change that he hasn't tested, then fix it later. This is a good reason why AUR packages specify a revision that the packager has compiled successfully, and hopefully ran well on his system.
Offline
SO, in order for you to get the LATEST code, you either have to edit the PKGBUILD to get the last revision, or wait for an update on the AUR.
Not strictly true. All -cvs and -svn and even mercurial pkgs within the AUR _should_ be compatible with versionpkg, which removes the need for such editing and should guarantee the latest version. I believe that aurbuild even has versionpkg integration these days
Offline
Pages: 1