SciTE - Editor of my choice
Sometimes you have to change your tools in order to keep your
productivity on a high level. Either it's your decision or the decision
of someone else which will force you to look for new methods. My present
employer decided to switch all workstations from *enter your favorite OS
here* to Windows XP. As I won't be able to install any tools in the
worst case I decided to look for an alternative to my current editor.
SciTE came into sight and after some customizing it works nicely for me.
However, as you could see in the screenshot, there seems to be a bug
with lexer and the highlighting. It's a Perl source file which is shown
and for an unknown reason he detection something around "information" as
a, uhm, whatever keyword. Sounds like a bug to me, I'll file it. Let's
hope they'll fix it soon.
References
Running a Subversion Server on Win32
Due to some circumstances I had to switch parts of my daily work
machines to Windows. Guess what, everyone is still complaining about
Windows, however I started to like it. Best part: try to set fonts for
the system! It's consistent everywhere - try that with GNOME and start a
KDE application. Oooops - did I start the bashing. Sorry for that.
Anyway, I had to look for some methods to get a Subversion server
running on Win32. Apache with the svn module is one option, however,
svnserve might be another option. Here are the steps required:
Install the binaries of Subversion:
Easy - mine had been installed in C:\Programme\Subversion\bin. The path
had already been added to the system path.
Setup a blank repository:
Still easy. I've setup mine in C:\Powerplant\code-repository\svn-repo.
In order to accomplish this the following commandlines are needed:
svnadmin create C:\Powerplant\code-repository\svn-repo
Edit the configuration:
In order to run a Subversion server you have to edit two config files. They are located inside C:\Powerplant\code-repository\svn-repo\conf. Their names are svnserve.conf and passwd. Let's have a look at the svnserve.conf file first. You need to enable three options inside the file. They are already in there, seek them and remove the hash in front of them. Save the file afterwards.
[general] ... anon-access = none auth-access = write ... password-db = passwdYou should also look inside the sasl thing. All the binaries of Subversion I found had sasl compiled it. It's general a good thing to encrypt your stuff so have a look how to enable it. However it's not necessary to get the server running.
Second will be the passwd file. Here are all the passwords for the user stored. The syntax is simple.
username = passwordIn this example the user with the name "username" and with the secret "password" is able to log in.
Start the daemon:
Here are two ways to manage this. Running the daemon inside a command box with the subcommand --daemon will work for some cases if you are not allowed to work inside the Win registry (like it will be at my workplace). Use a small batch file inside your autostart group for it.
svnserve --daemon -r C:\Powerplant\code-repository\svn-repoAnother way might be to enable the svnserve as Windows service. The commandline looks quite strange but I promise it will work this way. The syntax is in key= value style. Please note: there is a space before the value. If you don't do it that way the command will fail. If you'd used spaces inside your paths make sure to quote them. Quoting in general a good thing, I will include this inside my commandline here. Also please note - all the command has to be on one line!
C:\>sc create svnserve binPath= "C:\Programme\Subversion\bin\svnserve.exe
--service --root C:\Powerplant\code-repository\svn-repos"
DisplayName= "Subversion Server"
depend= tcpip start= auto
Link to the documentation:
Here is the full documentation for this: Windows Service Support for svnserve
German Perl Workshop 2009 / Deutscher Perl Workshop 2009
The workshop is over, I am finally fighting my flu, however everything
went very well for me. The two talks were quite successful and gave me
new opinions and changed my thoughts about details especially in the
field of the Reverse testing which will advance in the near future. The
workshop itself was well planned except that no WLAN was accessible. On
a conference I really would like to see a fast internet connection for
the people who attend. Give them the possibility to blog their thoughts,
share knowledge on the IRC channels, commit stuff to repositories, try
out the examples, etc.
As I said I already was fighting my cold
before my presentations so I was just lucky to be able to give them and
didn't care too much about the rest. In the future there might be a
split of the German Perl workshop - there are some discussions on the
mailinglist. Let's see whats going on there! Anyway - I prepared my
slides in German and English, I also did a recording of my speeches
which can be downloaded as MP3 now. So - here we go, thanks for your
interest everyone. See you at the next Perl workshop in 2010.
- Maintaining the best (German|PDF)
- Maintaining the best (English|PDF)
- Maintaining the best (Audio recording in German|MP3 ~21mb)
- Reverse Testing (German|PDF)
- Reverse Testing (English|PDF)
- Reverse Testing (Audio recording in German|MP3 ~9mb)
Perl presentation - Reverse Testing
I survived my talk (so far)... Anyway here are the slides for you.
Maintaing the best - Perl presentation
There is a still one hour left, I'll give my talk about maintaing Perl and Perl modules for pkgsrc at that time. Well, I am getting nervous - well, a little, might be fun :) Basically the talk shows some of the problems with Perl you'll encounter as a maintainer. Here are the slides for the presentation, I'll have a translated thing soon. After the presentation I will upload an audio recording of the speech.
