I was always a bit afraid to try those complex tools, but now with switch to subversion, I decided to give it a try. And it payed off. Now package management is much easier and everything is recorded in VCS. Yes I could do it with previously used bazaar too, but VCS migration was the latest impulse which made me try it. Now I can only thank to people who invented these tools.
…and imported into subversion. Today I walked over some older stuff in my CVS repository, I decided to import them also to subversion.
The only major unpublished thing there is Wessie. It was supposed to be modular publishing system written in PHP. However I lost interest in improving this during time and it was used only on two real life projects - one is site about Alcatel phones, which is still alive, the other one was our semester project for software engineering, which is now dead.
Anyway maybe somebody will find the sources useful, so feel free to do with sources whatever GNU GPL permits :-).
As continuation of migration to Subversion, Gammu now also uses Subversion as version control. This is now pretty standard version control system, so you can easily use latest development source.
Besides this, using Subversion brings us possibility to use various free services to work with this repository.
There might be also other useful tools, if you want some integration, just tell me.
I finally managed to migrate some things to Subversion from Bazaar. This does not yet include Gammu related things (Gammu, python-gammu and Wammu), because they are more tricky to migrate.
However all Debian packaging now can be handled using svn-buildpackage, which makes things a bit easier. Also smaller projects like Ukolovnik, polld and dictionary converter have been migrated.
You can see list of repositories at http://svn.cihar.com/, where is also link to web based browser.
Please note that repositories might change in future, because everything is not yet completely settled down.
I always wondered why there is no possiblity to create MP3 from Sound-Juicer. I expected it is some patent issue, but I have all lame stuff installed and expect things in GNOME to just work.
Unfortunately this is not the case, but Google works always and Jacob Emcken wrote down his configuration, so setup was quite easy. Thanks!
After more playing with Tailor, I managed to hack it enough to convert my Arch repositories to Subversion. Move from distributed to non distributed VCS migth look as step backwards, but I have pretty good reasons for this:
- Subversion is widely used and there is big chance that potential contributor will know how to use it. This lowers barrier for contributing (especially when compared to current Arch/Bazaar).
- Subversion sucks much less than CVS which is other well known VCS.
- If I want to work distributed I can still use Bazaar-NG with foreign branch features.
The conversion is currently on the way and will probably need some time (about half of Gammu revisions have been converted so far).
Well anything what has to be done manually sucks, so I scripted automatic generating of this documentation, so it should always be up to date with current development snapshot.
BTW: Anybody know how to document constructor of class implemented in C using EpyDoc? I didn't manage to find way for this.
After returning from Easter vacation, I was afraid of my full mailbox. This was quite correct, but fortunately some people also were not working, so it is not that bad. Anyway I didn't read it all so far, so don't be afraid if reaction on your mail (especially about Gammu and Wammu) will take longer.
The worst thing which happened was, that somebody managed to fuck up MySQL server serving phpMyAdmin demo in some very unusual way, which was not detected by my scripts, which are checking whether demo server is still alive. This lead to almost day outage, because I had to restore MySQL manually this morning. Anyway this case should be now also caught and the script for checking is getting more and more complex. Maybe I should better use Monit (or other monitoring software) for this instead of home made shell script. But shell script seems to do good job in most cases :-).
Off topic PS: Thanks to everybody who helped to release Debian 4.0!
I know that GNOME is trying to hide as much configuration as possible, but Epiphany today suprised me. I started to use is as default browser some time ago, but now I needed to print something for first time. Everything in my system is configured to use A4 paper, so I didn't expect any problem with this configuration.
Unforutanety Epiphany has separate configuration under separate menu item. I don't know why it is separated from print dialog, maybe to confuse users. Also I have no idea why it has default size Letter. Anyway you can set paper size under Print Setup...
This is really great step for usability.
Hmm, maybe it's time to look for some BTS with less security problems? The only problem is that I don't follow others that hard, so I maybe only don't know about such issues…