from small one page howto to huge articles all in one place
 

search text in:




Other .linuxhowtos.org sites: www.linuxhowtos.org
toolsntoys.linuxhowtos.org



Last additions:
How to make X listen on port 6000

How to make X listen on port 6000

words:

34

views:

36614

userrating:

average rating: 1.5 (4 votes) (1=very good 6=terrible)


May, 25th 2007:
April, 26th 2007:
Apr, 10th. 2007:
Druckversion . pdf icon
You are here: Tutorials per portage category->dev-util->cvs

Gentoo Linux CVS Tutorial


1. Introduction


Tutorial layout


This tutorial has two parts. The first shows you how to use CVS as a non-developer, i.e. how to get sources from CVS and keep them updated. The second part introduces you to using CVS as a developer, showing you how to modify, add and remove files on CVS and perform other developer-related tasks. If you are new to CVS, it's recommended that you begin in the first section and proceed to the second section; if you have some basic CVS experience but are going to be using CVS as a full-fledged developer for the first time, you should find everything you need in the second section, but you may want to go through the first section as a review.

What is CVS and what does it do?


CVS is a client/server system allowing developers to store their projects in a central location, called a repository. Using the cvs client tools, developers can make changes to the contents of the repository. In turn, the cvs repository tracks every change made to every file, creating a complete history of the evolution of the development project. Developers can request older versions of a particular source file, view a log of changes, and perform other useful tasks as needed.

The role of CVS


A lot of open software projects have their own CVS servers, which are used by the project developers as a central repository for all their work. Developers often make improvements to the sources in the CVS repository on a daily basis; and often, these developers are scattered around the world, yet CVS provides the necessary mechanism to unite their project into a centralized, cohesive whole. CVS creates the "organizational glue" that allows these developers to make improvements to the code without stepping on each other's toes, losing important data or missing each other's critical updates to particular source files.

CVS -- the latest developer sources


When the developers are ready, they'll roll some their current work on CVS into a .tar.gz file and release it as a new official version of their software package. However, the latest official release sometimes isn't recent enough, for a variety of possible reasons. In the first section of this tutorial, I'll show you how to use CVS for this purpose -- acquiring the latest and greatest developer version of the sources for your own personal use.

CVS -- do you have it?


Before you can actually use CVS, you need to get it installed on your system. The easiest way to test to see if it's installed is to type:
Code Listing 1.1: Starting CVS
# cvs

If a cvs command is found, then you've got it! Otherwise, you'll need to either track down a binary package for your particular distribution, or install it from sources. Installing CVS from sources is actually quite simple, and I'll show you how in the next panel.

Installing CVS from sources


Installing CVS from sources is easy. First, grab the cvs-1.11.tar.gz tarball from ftp://ftp.cvshome.org/pub/cvs-1.11/cvs-1.11.tar.gz (if there's a newer version listed
here, you might as well grab the new one instead.) Then perform the following steps (command output has been omitted for brevity):

Code Listing 1.2: Installing CVS using a tarball
# tar xzvf cvs-1.11.tar.gz      
# cd cvs-1.11
# ./configure
# make
# make install

Now you should be ready to go.

Installing CVS using a package management system


Many distributions provide an easy method to install software. For instance, the Gentoo distribution provides the emerge command. To install cvs, just type in emerge cvs:

Code Listing 1.3: Installing CVS using emerge
# emerge cvs

The CVSROOT


Before we begin, there are a few CVS fundamentals that you need to know. The first is that in order to connect to a CVS repository, you first need to know a path called the "CVSROOT". The CVSROOT is a string, like a URL, that tells the cvs command where the remote repository is and how we'd like to connect to it. Just to make things interesting, CVS has a number of CVSROOT formats, depending on whether the CVS repository is local or remote and what method you're going to use to connect to it. Here are some example CVSROOTs, along with explanations...

A local CVSROOT


Code Listing 1.4: Setting CVSROOT
CVSROOT=/var/cvsroot

This is an example of a local CVSROOT path; you'd use a CVSROOT like this if you wanted to connect to a local repository that exists at /var/cvsroot; or maybe you have a repository mounted via NFS at /var/cvsroot.

A remote password server CVSROOT


Code Listing 1.5: Setting CVSROOT with authentification
CVSROOT=:pserver:cvs@foo.bar.com:/var/cvsroot

Here's an example of a CVSROOT for a remote repository that exists on the foo.bar.com host and lives in the /var/cvsroot directory on that machine. The leading ":pserver:" part tells our client to connect to this remote machine using the CVS password server protocol, a protocol that's built-in to CVS. Typically, public CVS repositories use the password server protocol to allow access to anonymous users.

A remote rsh/ssh CVSROOT


Code Listing 1.6: RSH/SSH CVSROOT
CVSROOT=drobbins@foo.bar.com:/data/cvs

Here's an example of a CVSROOT that uses the RSH or SSH protocol; in this example, the CVS server will attempt to access the repository on foo.bar.com using the drobbins account. If the CVS_RSH environment variable is set to "ssh", then our cvs client will attempt to use ssh to connect; otherwise rsh will be used. The ssh access method is popular with those who are concerned about security; however, neither the RSH or SSH method provides a way for anonymous users to get the sources. In order to use this method, you must have a login account at foo.bar.com.

A few more things...


In addition to the CVSROOT, you'll also need to know the name of the module (collection of sources) that you'd like to check out, as well as an anonymous password that you'll need to log in to the CVS password server. Unlike anonymous ftp, there is no "standard" format for the anonymous password, so you'll need to get the specific password from the developer web site or the developers themselves. Once you have all this info, you're ready to begin.

Interacting with CVS, part 1


Grabbing the sources is a two-stage process. First, we log in to the password server. Then, we grab the sources with a checkout command. Here's an example set of commands that can be used to check out the latest Samba sources, a popular UNIX/Windows integration project:
Code Listing 1.7: Setting up CVSROOT
# export CVSROOT=:pserver:cvs@pserver.samba.org:/cvsroot

This first command sets the CVSROOT environment variable. If you don't set this variable, the following two commands will require an additional -d :pserver:cvs@pserver.samba.org:/cvsroot following the cvs command. Exporting the CVSROOT saves a us bit of typing.

Interacting with CVS, part 2


Here are the commands needed to get a current copy of the developer sources. You may want to jump forward to the next panel to read the explanation of these commands, and then jump back here:
Code Listing 1.8: Checking out sources
# cvs login      
(Logging in to cvs@pserver.samba.org)
CVS password: (enter password here)

# cvs -z5 co samba
U samba/COPYING
U samba/Manifest
U samba/README
U samba/Read-Manifest-Now
U samba/Roadmap
U samba/WHATSNEW.txt
(this is just a snippet of the complete cvs co output)

Interacting with CVS -- the explanation


The first cvs command above logs us in to the pserver, and the second tells our CVS client to check out ("co") the samba module using a gzip compression level of 5 ("-z5") to speed up the transfer over a slow link. For every new file that is created locally, cvs prints out a "U [path]" indicating that this particular file has been updated on disk.

Checkout complete


Once the checkout command completes, you'll see a "samba" directory in your current working directory that contains the latest sources. You'll also notice that all the directories have a "CVS" directory inside them -- CVS stores accounting information inside these directories, and they can safely be ignored. From this point forward, we don't need to worry about having the CVSROOT environment variable set nor do we need to specify it on the command line because it's now cached inside all those extra "CVS" directories. Remember -- you only need to have the CVSROOT set for the initial login and checkout.

Updating the sources


Well, there you are -- fresh sources! Now that you have the sources, you can go ahead and compile and install them, inspect them, or do whatever you like with them.

Every now and then, you may want to bring your checked-out source directory in-sync with the current version on CVS. To do this, you don't need to log in to the pserver again; your authentication info is also cached by cvs inside those "CVS" accounting directories. First, enter the main checked-out directory (in this case "samba"), and type:
Code Listing 1.9: Updating your sources
# cvs update -dP

Looking at "cvs update", part 1


If there are any new files, cvs will output "U [path]" lines for each one as it updates them. Also, if you compiled the sources, you will probably see a lot of "? [path]" lines; these are object files that cvs notices are not from the remote repository.

Looking at "cvs update", part 2


Also, notice the two command-line options we used for "cvs update". "-d" tells cvs to create any new directories that may have been added to the repository (this doesn't happen by default), and "-P" tells cvs to remove any empty directories from your locally checked-out copy of the sources. "-P" is a good idea, because cvs has a tendency to collect a lot of empty (once used, but now abandoned) directory trees over time.

When it comes to simply grabbing the latest sources, that's about all you need to know. Now, we take a look at how to interact with CVS as a developer.

2. CVS for developers


Modifying files


As a developer, you'll need to modify files on CVS. To do this, simply make the appropriate changes to your local copy of the repository. The changes you make to the sources are not applied to the remote repository until you explictly tell cvs to "commit" your changes. When you've tested all your modifications to ensure that they work properly and you're ready to apply your changes to the repository, follow this two-step process. First, update your sources by typing the following command in your main source directory:
Code Listing 2.1: Updating sources and directories
# cvs update -dP

CVS merges others' changes


As we've seen earlier, "cvs update" will bring your sources up-to-date with the current version in the repository -- but what happens to the changes you've made? Don't worry, they aren't thrown away. If another developer made changes to a file that you haven't touched, your local file will be updated so that it's in-sync with the version on the repository.
And, if you modified lines 1-10 of a local file, and another developer deleted lines 40-50, added 12 new lines at the end of the file, modified lines 30-40 and then committed their changes to the repository before you, cvs will intelligently merge these changes into your locally modified copy so that none of your changes are lost. This allows two or more developers to work on different parts of the same file at the same time.

Merging isn't perfect


However, if two or more developers have made changes to the same region of the same file, then things get a bit more complicated. If that happens, then cvs will tell you that there's been a conflict. No work will be lost, but a bit of manual intervention will be required, since cvs now requires your input on how to merge the conflicting changes.

The commit


We'll look at exactly how conflicts can be resolved in just a little bit, but for now, let's assume that there are no conflicts after you typed "cvs update -dP" -- there usually aren't. With no conflicts, your local sources are up-to-date, and you're ready to commit your changes to the repository by typing the following command in your main source directory:
Code Listing 2.2: Committing changes
# cvs commit

What commit does


"cvs commit" doesn't just apply your changes to the repository. Before actually committing your changes to the remote repository, cvs will fire up your default editor so that you can type in a description of your modifications. Once you've entered your comments, saved the file and exited the editor, your changes (and comments) will be applied to the remote repository and will be available to the other developers in your team.

Viewing the log


It's really easy to view the complete history of a particular file, along with any comments that the developers (including you) may have made when committing. To view this information, type:
Code Listing 2.3: View log information
# cvs log myfile.c

The "cvs log" command is recursive, so if you want to see the complete log for an entire directory tree, just enter the directory and type:
Code Listing 2.4: View log information with a pager
# cvs log | less

Commit options


You may want to use another editor than the one cvs starts by default when you type "cvs commit". If so, simply set the EDITOR environment variable to the name of the editor you want to use. Putting a setting such as this one in your ~/.bashrc would be a good idea:
Code Listing 2.5: Setting your editor
export EDITOR=jpico

Alternatively, you can also specify a log message as a command line option so that cvs doesn't need to load up an editor in the first place:
Code Listing 2.6: Committing changes with a small log information
# cvs commit -m 'I fixed a few silly bugs in portage.py'

The .cvsrc file


Before we continue looking at more cvs commands, I recommend setting up a ~/.cvsrc file. By creating a .cvsrc file in your home directory, you can tell cvs to use preferred command-line options by default so that you don't have to remember to type them in each time. Here's a recommended default .cvsrc file:
Code Listing 2.7: Recommended defaults
cvs -q        
diff -u -b -B
checkout -P
update -d -P

The .cvsrc file, continued


In addition to setting useful options for a bunch of cvs commands, the first line of the .cvsrc puts cvs into quiet mode, which has the primary benefit of making the cvs update output more consise and readable. Also, once you have this .cvsrc in place, you can type cvs update instead of typing cvs update -dP.

Adding a file to the repository


It's really easy to add a source file to CVS. First, create the file with your favorite text editor. Then, type the following:
Code Listing 2.8: Adding a file
# cvs add myfile.c  
cvs server: use 'cvs commit' to add this file permanently

This will tell cvs to add this file to the repository the next time you do a cvs commit. Until then, other developers won't be able to see it.

Adding a directory to the repository


The process of adding a directory to CVS is similar:
Code Listing 2.9: Adding a directory
# mkdir foo      
# cvs add foo
Directory /var/cvsroot/mycode/foo added to the repository

Unlike adding a file, when you add a directory it appears on the repository immediately; a cvs commit isn't required. Once you add a local directory to cvs, you'll notice that a "CVS" directory will be created inside it to serve as a container for cvs accounting data. Thus, you can easily tell if a particluar directory has been added to cvs by looking inside it for a "CVS" directory.

"cvs add" notes


Oh, and as you might guess, before you add a file or directory to the repository, you must make sure that its parent directory has already been added to CVS. Otherwise, you'll get an error that looks like this:
Code Listing 2.10: Adding a file, but receive a failure
# cvs add myfile.c      
cvs add: cannot open CVS/Entries for reading: No such file or directory
cvs [add aborted]: no repository

Getting familiar with "cvs update", part 1


Before we take a look at how to resolve conflicts, let's get familiar with the output of the "cvs update" command. If you created a ~/.cvsrc file that contains a "cvs -q" line, you'll find "cvs update" output a lot easier to read. "cvs update" informs you of what it does and sees by printing out a single character, a space, and a filename; as an example:
Code Listing 2.11: Updating CVS
# cvs update -dP      
? distfiles
? packages
? profiles

Getting familiar with "cvs update", part 2


"cvs update" uses the "?" character to tell you that it doesn't know anything about these particular files that it finds in the local copy of your repository. They're not officially part of the repository, nor have they been scheduled for addition. Here's a list of all the other single-character informational messages that CVS uses:
Code Listing 2.12: Informational message: U
U [path]

Used when a new file is created in your local repository, or an untouched (by you) file has been updated.
Code Listing 2.13: Informational message: A
A [path]

This file is scheduled for addition and will be officially added to the repository when you do a cvs commit.

Getting familiar with "cvs update", part 3


Code Listing 2.14: Informational message: R
R [path]

Like "A", an "R" lets you know that this file is scheduled for removal. The file will be removed from the repository as soon as you cvs commit.
Code Listing 2.15: Informational message: M
M [path]

This means that this file has been modified by you; additionally, it's possible that new changes from the repository were merged into this file successfully.
Code Listing 2.16: Informational message: C
C [path]

The "C" character indicates that this file has a conflict and requires manual fixing before you can "cvs commit" your changes.

Resolving conflicts intro


Now, let's take a look at how to resolve a conflict. I'm very involved in the Gentoo Linux project, and we have our own cvs server set up at cvs.gentoo.org. We developers spend most of our time hacking away at the sources inside the "gentoo-x86" module. Inside the gentoo-x86 module, we have a file called "ChangeLog" that houses (you guessed it) a description of the major changes we make to the files in the repository.

An example conflict


Because this file is modified nearly every time a developer makes a major change to CVS, it's a primary source of conflicts -- here's an example conflict. Let's say I add the following lines to the top of the ChangeLog:
Code Listing 2.17: ChangeLog entry
date 25 Feb 2001       
This is the thing I added myself

However, let's say that before I'm able to commit these three new lines, another developer adds these lines to the top of the ChangeLog and commits their changes:
Code Listing 2.18: ChangeLog entry 2
date 25 Feb 2001 
This is the part added by another developer

An example conflict, continued


Now, when I run cvs update -dP (as you should before every commit), cvs isn't able to merge the changes into my local copy of ChangeLog because we both have added lines to the exact same part of the file -- how is cvs to know which version to use? So, I get the following error from CVS:
Code Listing 2.19: CVS error
RCS file: /var/cvsroot/gentoo-x86/ChangeLog,v      
retrieving revision 1.362
retrieving revision 1.363
Merging differences between 1.362 and 1.363 into ChangeLog
rcsmerge: warning: conflicts during merge
cvs server: conflicts found in ChangeLog
C ChangeLog

Conflict resolution, part 1


Argh -- a conflict! Fortunately, fixing conflicts is easy. If I fire up my favorite text editor, I see the following text at the top of the ChangeLog file:
Code Listing 2.20: ChangeLog conflict
<<<<<<< ChangeLog 
date 25 Feb 2001
This is the thing I added myself

=======
date 25 Feb 2001
This is the part added by another developer

>>>>>>> 1.363

Conflict resolution, part 2


Instead of choosing one version over the other, cvs has added both versions to the ChangeLog file, and surrounded them with special separators to clearly mark the conflict in question. Now, it's up to me to replace this region with the text that should appear in ChangeLog; in this case, the replacement text is neither one or the other version but a combination of both:
Code Listing 2.21: ChangeLog entry
date 25 Feb 2001      
This is the thing I added myself
This is the part added by another developer

Now that I've replaced the conflicting region of the file with the appropriate text (and removed the "=======", etc markers), I can now commit my changes to cvs without any problems.

Conflict resolution tips


Whenever you need to edit a file for conflicts, make sure that you scan the entire file so that you catch all of them; if you forget to address a particular conflict, cvs won't allow you to commit until it's resolved! It's also obviously very important to remove the special markers that cvs added to the conflicting file. Another tip -- if you make a mistake while fixing the conflict and then ("D'oh!") accidentally save your changes, you can find an original copy of your version in the file ".#filename.version".

Removing a file


Now, it's time to learn our final CVS skill -- removing files from the repository. Removing a file is a two-stage process. First, delete the file from your local copy of the sources, and then execute the appropriate cvs remove command:
Code Listing 2.22: Removing a file
# rm myoldfile.c      
# cvs remove myoldfile.c

Removing a file, continued


The file will then be scheduled for removal from the repository the next time you do a commit. Once committed, the file will be officially deleted from the current version of the repository. However, cvs won't throw this file away, and will still keep a complete record of its contents and its history, just in case you need it back in the future. This is just one of the many ways that cvs protects your valuable source code.
cvs remove is recursive, which means that you can delete a bunch of files, and then run the cvs remove command with no other arguments from a parent directory. Doing this will cause all of the deleted files to be tagged for removal at the next commit.

Removing a directory


If you'd like to remove an entire directory, I recommend the following process. First, physically delete and "cvs remove" all files in the directory:
Code Listing 2.23: Removing a directory
# rm *.c      
# cvs remove

Removing a directory, continued


Then, perform a commit:
Code Listing 2.24: Commit your changes
# cvs commit

Here comes the trick. Perform the following steps to delete the directory:
Code Listing 2.25: Removing a directory      
# cd ..
# cvs remove mydir
# rm -rf mydir

Notice that removing the directory didn't require another commit -- directories are added to and removed from the repository in real-time.

Complete!


Your introduction to CVS is complete -- I hope that this tutorial has been helpful. There's much more to CVS than I've been able to cover in this introductory tutorial, but thankfully there are a bunch of great CVS resources you can use to further expand your CVS knowledge:

http://www.cvshome.org is the home of CVS development, and offers a bunch of documentation on CVS, including the official CVS documentation online
The CVS Version Control for Web Site Projects site has good info on how to use CVS for developing web sites
Karl Fogel has written a book called Open Source Development with CVS. A number of chapters are available for free from the website.
cvsweb is a really great CGI script that provides a web interface to your CVS repository; excellent for browsing.
The CVS Bubbles site has a bunch of good resources including a CVS FAQ-o-matic.

About this document


The original version of this article was first published on IBM developerWorks, and is property of Westtech Information Services. This document is an updated version of the original article, and contains various improvements made by the Gentoo Linux documentation team.

http://www.gentoo.org/doc/en/cvs-tutorial.xml
rate this article:
current rating: average rating: 1.0 (1 votes) (1=very good 6=terrible)
Your rating:
Very good (1) Good (2) ok (3) average (4) bad (5) terrible (6)

back
Please read "Why adblockers are bad".



other Ads
Stellenangebote
Stellenangebote
für Fach- und
Führungskräfte
www.nachoben.com
Trace My Cash
Wenn Sie sich schon immer mal gefragt haben, wo eigentlich Ihr geliebtes Bargeld geblieben ist, finden Sie hier vielleicht die Antwort.
www.tracemycash.com
Other free services
toURL.org
Shorten long
URLs to short
links like
http://tourl.org/2
tourl.org
.
Reverse DNS lookup
Find out which hostname(s)
resolve to a
given IP or other hostnames for the server
www.reversednslookup.org

New Packages

- as rdf newsfeed
- as rss newsfeed
- as Atom newsfeed
2017-01-22
abiword - 3.0.2-r1
Ebuild name:

app-office/abiword-3.0.2-r1

Description

Fully featured yet light and fast cross platform word processor

Added to portage

2017-01-22

abiword-docs - 3.0.2
Ebuild name:

app-office/abiword-docs-3.0.2

Description

Fully featured yet light and fast cross platform word processor docum

Added to portage

2017-01-22

asciidoctor - 1.5.5-r1
Ebuild name:

dev-ruby/asciidoctor-1.5.5-r1

Description

Processor for converting AsciiDoc into HTML 5, DocBook 4.5 and other

Added to portage

2017-01-22

auto-multiple-choice - 1.3.0
Ebuild name:

app-office/auto-multiple-choice-1.3.0

Description

Create and manage multiple choice questionnaries, including a

Added to portage

2017-01-22

aws-sdk - 2.6.50
Ebuild name:

dev-ruby/aws-sdk-2.6.50

Description

Official SDK for Amazon Web Services

Added to portage

2017-01-22

aws-sdk-core - 2.6.50
Ebuild name:

dev-ruby/aws-sdk-core-2.6.50

Description

Official SDK for Amazon Web Services

Added to portage

2017-01-22

aws-sdk-resources - 2.6.50
Ebuild name:

dev-ruby/aws-sdk-resources-2.6.50

Description

Official SDK for Amazon Web Services

Added to portage

2017-01-22

balsa - 2.5.3
Ebuild name:

mail-client/balsa-2.5.3

Description

Email client for GNOME

Added to portage

2017-01-22

blobby - 1.0
Ebuild name:

games-arcade/blobby-1.0

Description

A beach ball game with blobs of goo

Added to portage

2017-01-22

bson - 4.2.1
Ebuild name:

dev-ruby/bson-4.2.1

Description

A Ruby BSON implementation for MongoDB. (Includes binary C-based extension.)

Added to portage

2017-01-22

chromium - 56.0.2924.67
Ebuild name:

www-client/chromium-56.0.2924.67

Description

Open-source version of Google Chrome web browser

Added to portage

2017-01-22

chromium - 57.0.2986.0
Ebuild name:

www-client/chromium-57.0.2986.0

Description

Open-source version of Google Chrome web browser

Added to portage

2017-01-22

consul - 0.7.2
Ebuild name:

app-admin/consul-0.7.2

Description

A tool for service discovery, monitoring and configuration

Added to portage

2017-01-22

dar - 2.4.24
Ebuild name:

app-backup/dar-2.4.24

Description

A full featured backup tool, aimed for disks (floppy,CDR(W),DVDR(W),zip,jazz

Added to portage

2017-01-22

dar - 2.5.9
Ebuild name:

app-backup/dar-2.5.9

Description

A full featured backup tool, aimed for disks (floppy,CDR(W),DVDR(W),zip,jazz e

Added to portage

2017-01-22

eselect-mesa - 0.0.10-r1
Ebuild name:

app-eselect/eselect-mesa-0.0.10-r1

Description

Utility to change the Mesa OpenGL driver being used

Added to portage

2017-01-22

freeimage - 3.15.4-r1
Ebuild name:

media-libs/freeimage-3.15.4-r1

Description

Image library supporting many formats

Added to portage

2017-01-22

hexchat - 2.12.4-r2
Ebuild name:

net-irc/hexchat-2.12.4-r2

Description

Graphical IRC client based on XChat

Added to portage

2017-01-22

ignition-msgs - 0.7.0
Ebuild name:

net-libs/ignition-msgs-0.7.0

Description

Protobuf messages and functions for robot applications

Added to portage

2017-01-22

iso-codes - 3.74
Ebuild name:

app-text/iso-codes-3.74

Description

ISO language, territory, currency, script codes and their translations

Added to portage

2017-01-22

kcdemu - 0.7.2
Ebuild name:

app-cdr/kcdemu-0.7.2

Description

Frontend to cdemu daemon based on KDE Frameworks

Added to portage

2017-01-22

kicad - 4.0.5
Ebuild name:

sci-electronics/kicad-4.0.5

Description

Electronic Schematic and PCB design tools.

Added to portage

2017-01-22

kicad-doc - 4.0.5
Ebuild name:

app-doc/kicad-doc-4.0.5

Description

Electronic Schematic and PCB design tools manuals

Added to portage

2017-01-22

kramdown - 1.13.2-r1
Ebuild name:

dev-ruby/kramdown-1.13.2-r1

Description

Yet-another-markdown-parser but fast, pure Ruby, using strict syntax de

Added to portage

2017-01-22

libgtop - 2.34.2
Ebuild name:

gnome-base/libgtop-2.34.2

Description

A library that provides top functionality to applications

Added to portage

2017-01-22

libmypaint - 1.3.0
Ebuild name:

media-libs/libmypaint-1.3.0

Description

Library for making brushstrokes

Added to portage

2017-01-22

libyami - 1.1.0
Ebuild name:

media-libs/libyami-1.1.0

Description

Yet Another Media Infrastructure Media codec with hardware acceleration

Added to portage

2017-01-22

mednafen - 0.9.41
Ebuild name:

games-emulation/mednafen-0.9.41

Description

Argument-driven multi-system emulator utilizing OpenGL and SDL

Added to portage

2017-01-22

mypaint - 1.2.1
Ebuild name:

media-gfx/mypaint-1.2.1

Description

fast and easy graphics application for digital painters

Added to portage

2017-01-22

nautilus-tracker-tags - 1.8.3
Ebuild name:

gnome-extra/nautilus-tracker-tags-1.8.3

Description

Nautilus extension to tag files for Tracker

Added to portage

2017-01-22

ncpfs - 2.2.6-r4
Ebuild name:

net-fs/ncpfs-2.2.6-r4

Description

Provides access to Netware services using the NCP protocol

Added to portage

2017-01-22

os-prober - 1.73
Ebuild name:

sys-boot/os-prober-1.73

Description

Utility to detect other OSs on a set of drives

Added to portage

2017-01-22

packagekit - 1.1.5
Ebuild name:

app-admin/packagekit-1.1.5

Description

PackageKit Package Manager interface (meta package)

Added to portage

2017-01-22

packagekit-base - 1.1.5
Ebuild name:

app-admin/packagekit-base-1.1.5

Description

Manage packages in a secure way using a cross-distro and cross-arch

Added to portage

2017-01-22

packagekit-gtk - 1.1.5
Ebuild name:

app-admin/packagekit-gtk-1.1.5

Description

Gtk3 PackageKit backend library

Added to portage

2017-01-22

pdf-core - 0.6.1-r1
Ebuild name:

dev-ruby/pdf-core-0.6.1-r1

Description

Implements low level PDF features for Prawn

Added to portage

2017-01-22

pdf-inspector - 1.2.1-r1
Ebuild name:

dev-ruby/pdf-inspector-1.2.1-r1

Description

A tool for analyzing PDF output

Added to portage

2017-01-22

pdf-reader - 1.4.1-r1
Ebuild name:

dev-ruby/pdf-reader-1.4.1-r1

Description

PDF parser conforming as much as possible to the PDF specification fro

Added to portage

2017-01-22

prawn - 2.1.0-r1
Ebuild name:

dev-ruby/prawn-2.1.0-r1

Description

Fast, Nimble PDF Generation For Ruby

Added to portage

2017-01-22

prawn-table - 0.2.2-r1
Ebuild name:

dev-ruby/prawn-table-0.2.2-r1

Description

Provides support for tables in Prawn

Added to portage

2017-01-22

psh - 1.8.1-r3
Ebuild name:

app-shells/psh-1.8.1-r3

Description

Combines the interactive nature of a Unix shell with the power of Perl

Added to portage

2017-01-22

pyatspi - 2.20.3
Ebuild name:

dev-python/pyatspi-2.20.3

Description

Python binding to at-spi library

Added to portage

2017-01-22

pycups - 1.9.73-r1
Ebuild name:

dev-python/pycups-1.9.73-r1

Description

Python bindings for the CUPS API

Added to portage

2017-01-22

qscintilla-python - 2.9.4-r1
Ebuild name:

dev-python/qscintilla-python-2.9.4-r1

Description

Python bindings for Qscintilla

Added to portage

2017-01-22

roboto - 2.136
Ebuild name:

media-fonts/roboto-2.136

Description

Standard font for Android 4.0 (Ice Cream Sandwich) and later

Added to portage

2017-01-22

setuptools - 33.1.1
Ebuild name:

dev-python/setuptools-33.1.1

Description

Collection of extensions to Distutils

Added to portage

2017-01-22

slack-bin - 2.4.2
Ebuild name:

net-im/slack-bin-2.4.2

Description

Team collaboration tool

Added to portage

2017-01-22

suitesparseconfig - 4.2.1-r1
Ebuild name:

sci-libs/suitesparseconfig-4.2.1-r1

Description

Common configurations for all packages in suitesparse

Added to portage

2017-01-22

tracker - 1.8.3
Ebuild name:

app-misc/tracker-1.8.3

Description

A tagging metadata database, search tool and indexer

Added to portage

2017-01-22

yadm - 1.06
Ebuild name:

app-admin/yadm-1.06

Description

A dotfile manager for the config files in your home folder

Added to portage

2017-01-22

2017-01-21
CPAN-Perl-Releases - 3.80.0
Ebuild name:

dev-perl/CPAN-Perl-Releases-3.80.0

Description

Mapping Perl releases on CPAN to the location of the tarballs

Added to portage

2017-01-21

Sys-Virt - 2.5.0
Ebuild name:

dev-perl/Sys-Virt-2.5.0

Description

API for using the libvirt library from Perl

Added to portage

2017-01-21

airdcpp-webclient - 1.4.1
Ebuild name:

net-p2p/airdcpp-webclient-1.4.1

Description

Cross-platform Direct Connect client

Added to portage

2017-01-21

argp-standalone - 1.3-r2
Ebuild name:

sys-libs/argp-standalone-1.3-r2

Description

Standalone argp library for use with uclibc

Added to portage

2017-01-21

audiofile - 0.3.6-r3
Ebuild name:

media-libs/audiofile-0.3.6-r3

Description

An elegant API for accessing audio files

Added to portage

2017-01-21

aufs-sources - 3.18.47
Ebuild name:

sys-kernel/aufs-sources-3.18.47

Description

Full sources including the Gentoo patchset for the linux kernel tre

Added to portage

2017-01-21

aufs-sources - 4.4.43
Ebuild name:

sys-kernel/aufs-sources-4.4.43

Description

Full sources including the Gentoo patchset for the linux kernel tree

Added to portage

2017-01-21

aufs-sources - 4.4.44
Ebuild name:

sys-kernel/aufs-sources-4.4.44

Description

Full sources including the Gentoo patchset for the linux kernel tree

Added to portage

2017-01-21

aufs-sources - 4.9.4
Ebuild name:

sys-kernel/aufs-sources-4.9.4

Description

Full sources including the Gentoo patchset for the linux kernel tree

Added to portage

2017-01-21

aufs-sources - 4.9.5
Ebuild name:

sys-kernel/aufs-sources-4.9.5

Description

Full sources including the Gentoo patchset for the linux kernel tree

Added to portage

2017-01-21

aws-sigv4 - 1.0.0
Ebuild name:

dev-ruby/aws-sigv4-1.0.0

Description

Amazon Web Services Signature Version 4 signing library

Added to portage

2017-01-21

bash - 4.4_p11
Ebuild name:

app-shells/bash-4.4_p11

Description

The standard GNU Bourne again shell

Added to portage

2017-01-21

bitlbee - 3.5
Ebuild name:

net-im/bitlbee-3.5

Description

irc to IM gateway that support multiple IM protocols

Added to portage

2017-01-21

bup - 0.29
Ebuild name:

app-backup/bup-0.29

Description

A highly efficient backup system based on the git packfile format

Added to portage

2017-01-21

calendar - 0.9.1-r1
Ebuild name:

app-misc/calendar-0.9.1-r1

Description

Standard unix calendar program for Linux, ported from OpenBSD

Added to portage

2017-01-21

celery - 4.0.2
Ebuild name:

dev-python/celery-4.0.2

Description

Asynchronous task queue/job queue based on distributed message passing

Added to portage

2017-01-21

chrome-binary-plugins - 56.0.2924.67_beta
Ebuild name:

www-plugins/chrome-binary-plugins-56.0.2924.67_beta

Description

Binary plugins from Google Chrome for use in Ch

Added to portage

2017-01-21

chrome-binary-plugins - 57.0.2986.0_alpha
Ebuild name:

www-plugins/chrome-binary-plugins-57.0.2986.0_alpha

Description

Binary plugins from Google Chrome for use in Ch

Added to portage

2017-01-21

ck-sources - 4.9.5
Ebuild name:

sys-kernel/ck-sources-4.9.5

Description

Con Kolivas' high performance patchset and Gentoo's genpatches for Linu

Added to portage

2017-01-21

crystal - 0.20.5
Ebuild name:

dev-lang/crystal-0.20.5

Description

The Crystal Programming Language

Added to portage

2017-01-21

dwm - 6.1-r1
Ebuild name:

x11-wm/dwm-6.1-r1

Description

a dynamic window manager for X11

Added to portage

2017-01-21

dwm - 9999
Ebuild name:

x11-wm/dwm-9999

Description

a dynamic window manager for X11

Added to portage

2017-01-21

epiphany - 3.20.6
Ebuild name:

www-client/epiphany-3.20.6

Description

GNOME webbrowser based on Webkit

Added to portage

2017-01-21

erlang - 19.2
Ebuild name:

dev-lang/erlang-19.2

Description

Erlang programming language, runtime environment and libraries (OTP)

Added to portage

2017-01-21

filebeat - 5.1.2
Ebuild name:

app-admin/filebeat-5.1.2

Description

Lightweight log shipper for Logstash and Elasticsearch

Added to portage

2017-01-21

flake8 - 3.2.1
Ebuild name:

dev-python/flake8-3.2.1

Description

A wrapper around PyFlakes, pep8 & mccabe

Added to portage

2017-01-21

freetype - 2.7.1-r1
Ebuild name:

media-libs/freetype-2.7.1-r1

Description

A high-quality and portable font engine

Added to portage

2017-01-21

gennodejs - 2.0.0
Ebuild name:

dev-ros/gennodejs-2.0.0

Description

Javascript ROS message and service generators

Added to portage

2017-01-21

geoip-python - 1.3.2-r1
Ebuild name:

dev-python/geoip-python-1.3.2-r1

Description

Python bindings for GeoIP

Added to portage

2017-01-21

google-chrome-beta - 56.0.2924.67
Ebuild name:

www-client/google-chrome-beta-56.0.2924.67

Description

The web browser from Google

Added to portage

2017-01-21

google-chrome-unstable - 57.0.2986.0
Ebuild name:

www-client/google-chrome-unstable-57.0.2986.0

Description

The web browser from Google

Added to portage

2017-01-21

gpsbabel - 1.5.4
Ebuild name:

sci-geosciences/gpsbabel-1.5.4

Description

GPS waypoints, tracks and routes converter

Added to portage

2017-01-21

i3status - 2.11
Ebuild name:

x11-misc/i3status-2.11

Description

generates a status bar for dzen2, xmobar or similar

Added to portage

2017-01-21

imagemagick - 6.9.7.4
Ebuild name:

media-gfx/imagemagick-6.9.7.4

Description

A collection of tools and libraries for many image formats

Added to portage

2017-01-21

imagemagick - 7.0.4.4
Ebuild name:

media-gfx/imagemagick-7.0.4.4

Description

A collection of tools and libraries for many image formats

Added to portage

2017-01-21

libvncserver - 0.9.11-r1
Ebuild name:

net-libs/libvncserver-0.9.11-r1

Description

library for creating vnc servers

Added to portage

2017-01-21

llvm - 3.9.1-r1
Ebuild name:

sys-devel/llvm-3.9.1-r1

Description

Low Level Virtual Machine

Added to portage

2017-01-21

mccabe - 0.5.3
Ebuild name:

dev-python/mccabe-0.5.3

Description

flake8 plugin McCabe complexity checker

Added to portage

2017-01-21

mod_wsgi - 4.5.13
Ebuild name:

www-apache/mod_wsgi-4.5.13

Description

An Apache2 module for running Python WSGI applications

Added to portage

2017-01-21

mpv-bash-completion - 3.3.8
Ebuild name:

app-shells/mpv-bash-completion-3.3.8

Description

Bash completion for the mpv video player

Added to portage

2017-01-21

networkmanager - 1.4.4-r1
Ebuild name:

net-misc/networkmanager-1.4.4-r1

Description

A set of co-operative tools that make networking simple and straig

Added to portage

2017-01-21

obstack-standalone - 1.1
Ebuild name:

sys-libs/obstack-standalone-1.1

Description

A standalone library to implement GNU libc's obstack.

Added to portage

2017-01-21

opus - 1.1.3-r1
Ebuild name:

media-libs/opus-1.1.3-r1

Description

Open codec designed for internet transmission of interactive speech and au

Added to portage

2017-01-21

puppet-lint - 2.1.0
Ebuild name:

app-admin/puppet-lint-2.1.0

Description

A linter for puppet DSL

Added to portage

2017-01-21

pylibmc - 1.5.1-r1
Ebuild name:

dev-python/pylibmc-1.5.1-r1

Description

Libmemcached wrapper written as a Python extension

Added to portage

2017-01-21

pytest-runner - 2.10.1
Ebuild name:

dev-python/pytest-runner-2.10.1

Description

Adds support for tests during installation of setup.py files

Added to portage

2017-01-21

python-distutils-extra - 2.39
Ebuild name:

dev-python/python-distutils-extra-2.39

Description

Gettext support, themed icons and scrollkeeper-based documen

Added to portage

2017-01-21

pytools - 2016.2.6
Ebuild name:

dev-python/pytools-2016.2.6

Description

A collection of tools missing from the Python standard library

Added to portage

2017-01-21

rebar - 2.6.3
Ebuild name:

dev-util/rebar-2.6.3

Description

A sophisticated build-tool for Erlang projects that follows OTP principles

Added to portage

2017-01-21

ripgrep - 0.4.0
Ebuild name:

sys-apps/ripgrep-0.4.0

Description

a command line search tool that combines usability with raw speed

Added to portage

2017-01-21

rspamd - 1.4.3
Ebuild name:

mail-filter/rspamd-1.4.3

Description

Rapid spam filtering system

Added to portage

2017-01-21

rubygems - 2.6.9
Ebuild name:

dev-ruby/rubygems-2.6.9

Description

Centralized Ruby extension management system

Added to portage

2017-01-21

shapelib - 1.4.0
Ebuild name:

sci-libs/shapelib-1.4.0

Description

Library for manipulating ESRI Shapefiles

Added to portage

2017-01-21

snappy - 0.5-r3
Ebuild name:

dev-python/snappy-0.5-r3

Description

Python library for the snappy compression library from Google

Added to portage

2017-01-21

swig - 3.0.11
Ebuild name:

dev-lang/swig-3.0.11

Description

Simplified Wrapper and Interface Generator

Added to portage

2017-01-21

symlinks - 1.4-r3
Ebuild name:

app-misc/symlinks-1.4-r3

Description

Scans for and fixes broken or messy symlinks

Added to portage

2017-01-21

texlive - 2016
Ebuild name:

app-text/texlive-2016

Description

A complete TeX distribution

Added to portage

2017-01-21

texlive-basic - 2016
Ebuild name:

dev-texlive/texlive-basic-2016

Description

TeXLive Essential programs and files

Added to portage

2017-01-21

texlive-bibtexextra - 2016
Ebuild name:

dev-texlive/texlive-bibtexextra-2016

Description

TeXLive BibTeX additional styles

Added to portage

2017-01-21

texlive-context - 2016
Ebuild name:

dev-texlive/texlive-context-2016

Description

TeXLive ConTeXt and packages

Added to portage

2017-01-21

texlive-core - 2016
Ebuild name:

app-text/texlive-core-2016

Description

A complete TeX distribution

Added to portage

2017-01-21

texlive-fontsextra - 2016
Ebuild name:

dev-texlive/texlive-fontsextra-2016

Description

TeXLive Additional fonts

Added to portage

2017-01-21

texlive-fontsrecommended - 2016
Ebuild name:

dev-texlive/texlive-fontsrecommended-2016

Description

TeXLive Recommended fonts

Added to portage

2017-01-21

texlive-fontutils - 2016
Ebuild name:

dev-texlive/texlive-fontutils-2016

Description

TeXLive Graphics and font utilities

Added to portage

2017-01-21

texlive-formatsextra - 2016
Ebuild name:

dev-texlive/texlive-formatsextra-2016

Description

TeXLive Additional formats

Added to portage

2017-01-21

texlive-games - 2016
Ebuild name:

dev-texlive/texlive-games-2016

Description

TeXLive Games typesetting

Added to portage

2017-01-21

texlive-genericextra - 2016
Ebuild name:

dev-texlive/texlive-genericextra-2016

Description

TeXLive Generic additional packages

Added to portage

2017-01-21

texlive-genericrecommended - 2016
Ebuild name:

dev-texlive/texlive-genericrecommended-2016

Description

TeXLive Generic recommended packages

Added to portage

2017-01-21

texlive-humanities - 2016
Ebuild name:

dev-texlive/texlive-humanities-2016

Description

TeXLive Humanities packages

Added to portage

2017-01-21

texlive-langafrican - 2016
Ebuild name:

dev-texlive/texlive-langafrican-2016

Description

TeXLive African scripts

Added to portage

2017-01-21

texlive-langarabic - 2016
Ebuild name:

dev-texlive/texlive-langarabic-2016

Description

TeXLive Arabic

Added to portage

2017-01-21

texlive-langchinese - 2016
Ebuild name:

dev-texlive/texlive-langchinese-2016

Description

TeXLive Chinese

Added to portage

2017-01-21

texlive-langcjk - 2016
Ebuild name:

dev-texlive/texlive-langcjk-2016

Description

TeXLive Chinese/Japanese/Korean (base)

Added to portage

2017-01-21

texlive-langcyrillic - 2016
Ebuild name:

dev-texlive/texlive-langcyrillic-2016

Description

TeXLive Cyrillic

Added to portage

2017-01-21

texlive-langczechslovak - 2016
Ebuild name:

dev-texlive/texlive-langczechslovak-2016

Description

TeXLive Czech/Slovak

Added to portage

2017-01-21

texlive-langenglish - 2016
Ebuild name:

dev-texlive/texlive-langenglish-2016

Description

TeXLive US and UK English

Added to portage

2017-01-21

texlive-langeuropean - 2016
Ebuild name:

dev-texlive/texlive-langeuropean-2016

Description

TeXLive Other European languages

Added to portage

2017-01-21

texlive-langfrench - 2016
Ebuild name:

dev-texlive/texlive-langfrench-2016

Description

TeXLive French

Added to portage

2017-01-21

texlive-langgerman - 2016
Ebuild name:

dev-texlive/texlive-langgerman-2016

Description

TeXLive German

Added to portage

2017-01-21

texlive-langgreek - 2016
Ebuild name:

dev-texlive/texlive-langgreek-2016

Description

TeXLive Greek

Added to portage

2017-01-21

texlive-langindic - 2016
Ebuild name:

dev-texlive/texlive-langindic-2016

Description

TeXLive Indic scripts

Added to portage

2017-01-21

texlive-langitalian - 2016
Ebuild name:

dev-texlive/texlive-langitalian-2016

Description

TeXLive Italian

Added to portage

2017-01-21

texlive-langjapanese - 2016
Ebuild name:

dev-texlive/texlive-langjapanese-2016

Description

TeXLive Japanese

Added to portage

2017-01-21

texlive-langkorean - 2016
Ebuild name:

dev-texlive/texlive-langkorean-2016

Description

TeXLive Korean

Added to portage

2017-01-21

texlive-langother - 2016
Ebuild name:

dev-texlive/texlive-langother-2016

Description

TeXLive Other languages

Added to portage

2017-01-21

texlive-langpolish - 2016
Ebuild name:

dev-texlive/texlive-langpolish-2016

Description

TeXLive Polish

Added to portage

2017-01-21

texlive-langportuguese - 2016
Ebuild name:

dev-texlive/texlive-langportuguese-2016

Description

TeXLive Portuguese

Added to portage

2017-01-21

texlive-langspanish - 2016
Ebuild name:

dev-texlive/texlive-langspanish-2016

Description

TeXLive Spanish

Added to portage

2017-01-21

texlive-latex - 2016
Ebuild name:

dev-texlive/texlive-latex-2016

Description

TeXLive LaTeX fundamental packages

Added to portage

2017-01-21

texlive-latexextra - 2016
Ebuild name:

dev-texlive/texlive-latexextra-2016

Description

TeXLive LaTeX additional packages

Added to portage

2017-01-21

texlive-latexrecommended - 2016
Ebuild name:

dev-texlive/texlive-latexrecommended-2016

Description

TeXLive LaTeX recommended packages

Added to portage

2017-01-21

texlive-luatex - 2016
Ebuild name:

dev-texlive/texlive-luatex-2016

Description

TeXLive LuaTeX packages

Added to portage

2017-01-21

texlive-mathscience - 2016
Ebuild name:

dev-texlive/texlive-mathscience-2016

Description

TeXLive Mathematics and science packages

Added to portage

2017-01-21

texlive-metapost - 2016
Ebuild name:

dev-texlive/texlive-metapost-2016

Description

TeXLive MetaPost and Metafont packages

Added to portage

2017-01-21

texlive-music - 2016
Ebuild name:

dev-texlive/texlive-music-2016

Description

TeXLive Music packages

Added to portage

2017-01-21

texlive-omega - 2016
Ebuild name:

dev-texlive/texlive-omega-2016

Description

TeXLive Omega packages

Added to portage

2017-01-21

texlive-pictures - 2016
Ebuild name:

dev-texlive/texlive-pictures-2016

Description

TeXLive Graphics, pictures, diagrams

Added to portage

2017-01-21

texlive-plainextra - 2016
Ebuild name:

dev-texlive/texlive-plainextra-2016

Description

TeXLive Plain TeX packages

Added to portage

2017-01-21

texlive-pstricks - 2016
Ebuild name:

dev-texlive/texlive-pstricks-2016

Description

TeXLive PSTricks

Added to portage

2017-01-21

texlive-publishers - 2016
Ebuild name:

dev-texlive/texlive-publishers-2016

Description

TeXLive Publisher styles, theses, etc.

Added to portage

2017-01-21

texlive-xetex - 2016
Ebuild name:

dev-texlive/texlive-xetex-2016

Description

TeXLive XeTeX and packages

Added to portage

2017-01-21

tmux - 2.3-r1
Ebuild name:

app-misc/tmux-2.3-r1

Description

Terminal multiplexer

Added to portage

2017-01-21

util-linux - 2.29.1
Ebuild name:

sys-apps/util-linux-2.29.1

Description

Various useful Linux utilities

Added to portage

2017-01-21

webkit-gtk - 2.14.3
Ebuild name:

net-libs/webkit-gtk-2.14.3

Description

Open source web browser engine

Added to portage

2017-01-21

weechat - 1.7
Ebuild name:

net-irc/weechat-1.7

Description

Portable and multi-interface IRC client

Added to portage

2017-01-21

rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004 S&P Softwaredesign
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 8.6 ms
system status display
Stellenangebote