Tuesday, February 18. 2014
Waiting for a STATE folder in the XDG basedir spec
The XDG Basedirectory specification proposes default homedir folders for the categories DATA (~/.local/share), CONFIG (~/.config) and CACHE (~/.cache). One category however is missing: STATE. This category has been requested several times but nothing happened.
Examples for state data are:
The missing STATE category is especially annoying if you're managing your dotfiles with a VCS (e.g. via VCSH) and you care to keep your homedir tidy.
If you're as annoyed as me about the missing STATE category, please voice your opinion on the XDG mailing list.
Of course it's a very long way until applications really use such a STATE directory. But without a common standard it will never happen.
Friday, January 28. 2011
Google Summer of Code 2011
This summer I'll be a full time student (again) to finish my computer science bachelor. So I thought it would be a nice occasion to apply for the Google Summer of Code. Would anybody like to recommend me a project? Something around Debian, Java, decentralized social software, quality assurance or developer tools?
Sunday, May 16. 2010
tnt is not topgit
As I've already written, I'm working on an alternative to topgit. I made a first attempt in perl some weeks ago, but gave up after some frustrating hours. Yesterday I started again in python and had a very nice time putting together the groundwork and the first two commands.
It may be noted, that I've no previous programming experience in neither perl nor python!
By now, I can create a patchset branch and add a patch branch to it. There's still a lot to do. For my talk at the Debian Mini Conference in Berlin next month I'd like to be able to update patch branches, export patchsets and give a status summary.
Maybe I can already find somebody who's interested in joining me with this project? The code is in my github account, however the name will most probably change.
One reason that I've been much faster in python is the fantastic python-git library. I can only recommend it!
In other news: I'm searching a couch to surf in Berlin from june 7.-12. I prefer couchsurfing over hotels mostly to get to know nice people around the world. Please contact me, if you'd like to host me for a night or two. (thomas at koch punkt ro)
Update: Slides of my talk at the debconf are available.
Friday, April 2. 2010
Design document for a patch management system on a DVCS
Dear friends of Debian,
this is my first post to Planet Debian. - The planet with the most geeky registration procedure in the known universe!
I proposed an alternative to topgit some days ago on the vcs-pkg.org list. Martin asked (and encouraged) me to give a better explanation of the idea, which I'll hereby try. Sorry for not giving any drawings, but I'm totally incapable of anything graphical.
Hopefully, I'll manage to come to the Debian Miniconf in Berlin. Then we could discuss the idea further and maybe even start implementing it. (Somebody would need to help me with my first steps in Perl then...)
The following text is available on github. Please help me expand it!
Design document for a patch management system on a DVCS
The system to implement manages patchsets. A patchset is a set of patches with a tree-ish dependency graph between the patches. There's one distinct root of this dependency graph.
Patches are managed as branches with each branch representing a patch. Modification of a patch is done by a commit to the respective branch. A branch representing a patch as part of a patchset is called patchbranch.
The patch of a patchbranch is created as the diff between the root of the patchbranch and the head.
The most important management methods are:
patchset meta branch
A patchset meta branch holds all informations about one patchset. First, it holds references to the top commits of all patch branches in the form of parent references of commits. Thus pushing the patchset meta branch automatically also pushes all commits of all patch branches.
Secondly, the patchset meta branch contains meta informations about the patchset. These meta informations are:
Since the patchset meta branch holds all this informations, it is possible, to delete all patch branches and recreate them from this informations.
Although the commits of the patchset meta branches hold references to the patch branches, its file tree does not need to contain any files from the referenced patches. This may confuse the underlying DVCS, but the patch meta branch is not ment to be directly inspected.
The branches file
A branches file for a fictive patchset could look like:
# patch branches without an explicit dependency depend on the root of the # patchset tree # A Root can be given as either a fix commit (seen here), a branch or a tag. # A fixed commit or tag is useful to maintain a patchset against an older # upstream version ROOT: 6a8589de32d490806ab86432a3181370e65953ca # A tag as a dependency #ROOT: upstream/0.1.2 # A branch as a dependency #ROOT: upstream # A regular patch with it's name and last commit BRANCH: debian/use-debian-jars-in-build-xml 4bab542c261ff1a1ae87151c3536f19ef02d7937 # two other regular patches BRANCH: upstream-jira/HDFS-1234 a8e4af13106582ca1bfbbcaeb0537f73faf46d87 BRANCH: upstream-jira/MAP-REDUCE-007 e3426bcbcb2537478f851edcf6eb04b34f6c7106 # This patch depends on the above two patches # The sha1 below the dependency patches references a merge commit of the two # dependencies BRANCH: upstream-jira/HDFS-008 517851aa829d77e09bc5e59985fed1b0aa339cc6 DEPENDENCIES: upstream-jira/HDFS-1234 upstream-jira/MAP-REDUCE-007 cc294f2e4773c4ff71efb83648a0e16835fca841 # A patch branch that belongs to the patch branch, but won't get exported (yet) BRANCH: upstream-jira/HDFS-9999 74257905azgsa4689bc5e59985fed1b0aa339cc6 BRANCH-FLAGS: noexport