linuxwacom and xf86-input-wacom plan

X.org is helping us porting Wacom driver into a public git repository at freedesktop.org so linuxwacom xorg driver (called xf86-input-wacom there) will be in-sync with future xorg releases. The current plan is to make xf86-input-wacom at freedesktop ( temporarily parked at http://cgit.freedesktop.org/~whot/xf86-input-wacom/) the primary repository for xserver 1.6 and later.  I will create a new linuxwacom CVS branch here to include the kernel drivers, utility programs, etc for xserver 1.6 and later.  The xf86-input-wacom that sits inside the new linuxwacom branch will be a clone of the freedesktop.org one. So, hopefully, xserver 1.6 and later users will soon get an linuxwacom package that contains the same functionalities available now for xservers older than 1.6. All future patches for xf86-input-wacom will be merged into the freedesktop.org repository.

 

I know quite a few developers here have been waiting for this moment with anxiety for a while. I am sure you know what I am going to say next: we need help :).

 

We are working hard to get it in-sync with X11R7.5. However, with Peter, the X.org powerhouse, has to spend most of his time for the coming X11R7.5 release and me working on new tablet support, we are really short of hands.  Please, if you have time, help us bring the current xf86-input-wacom in sync with the APIs and structures similar to evdev ( http://cgit.freedesktop.org/xorg/driver/xf86-input-evdev) and/or synaptics ( http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics).  Below is a list of the basic steps that are provided by Peter.  With these steps, you can clone the current xf86-input-wacom off Peter's local repository and compile/update/test it on a system that is running xorg server 1.6 or later.  Please email your patches here and cc to Peter ( peter.hutterer@...).  Thank you all in advance for your support and participation.

 

Ping

 

-----------------------------------------------------------------------------------------------

Before starting the real work, please do the following so your information will be displayed in the repository's history (we'd love to give credit where credit is due):

git config --global user.name "Your Name"
git config --global user.email "your email address"

Note that xf86-input-wacom is managed in git and thus the development
workflow is slightly different to projects managed in CVS. For once, each
copy of the repository is it's own repository in itself. Amongst other
things this allows you to develop and commit locally without affecting the
original repository. A short outline of the workflow is below, please refer
to a git tutorial of your choice for a more detailed description on how to
use git.

Getting the repository ("cloning" the repository):
$ git clone git://people.freedesktop.org/~whot/xf86-input-wacom.git

This creates a local copy of the repository (referred to as "origin"). You
can commit to it without affecting the remote repository itself. Bu default,
the repository is on the "master" branch. If you wish to check out another
branch, run the following command:

$ git branch -a # displays all branches, local and remote
$ git checkout -b <branchname> origin/<branchname>

This checks out the branch <branchname> from the remote repository into your
local branch <branchname>.
You can switch back to the master branch simply by running
$ git checkout master

To get the local history, try one of either:
$ git log      # similar to cvs log
$ gitk         # graphical tool
$ tig          # ncurses based tool

To commit to your local repository:
$ git commit -a # commit everything
$ git commit <filename> <filename> ...

As said above, a commit only affects your local repository, so feel free to
commit as often as you want.

If you want to send a patch to us, try:
$ git format-patch HEAD~1  # just the last commit as patch
$ git format-patch HEAD~5.. # the last 5 commits as patches
$ git format-patch origin/master.. # all commits since origin's master

It's advisable to sync often with the remote repository, especially before
sending a patch:
$ git pull --rebase

This gets all changes from the remote repository and puts your patches on
top of it (you may have to fix some merge commits, see the man page for git
rebase).

Note that this is an incomplete list of git features, we really recommend to
walk through a tutorial first (http://www.kernel.org/pub/software/scm/git/docs/user-manual.html). Git is intimidatingly powerful at first but
once you get used to the workflows it becomes very convenient.

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel