Ever called a perl script and got this?

Can't locate Regexp/Common.pm in @INC (@INC contains: SCRIPT /usr/lib/perl5/5.10.0/i586-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/site_perl/5.10.0/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.10.0 /usr/lib/perl5/vendor_perl/5.10.0/i586-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl .) at SCRIPT line 18.

Well, use zypper:

coolo@desdemona#STABLE>sudo zypper in -C 'perl(Regexp::Common)'
Reading installed packages...

The following NEW package is going to be installed:
perl-Regexp-Common

Easy, no?

Well, was a huge journey for usr this time. 2008.1 was not only an updated 2008.0, but since early design, was clearly that we would try do a big step on our development. Just to mention what arrived since 2008.0, we're integrated Manbo labs work, which means now we're have a real common core system between us and Turbo Linux, we're integrated PulseAudio on whole distro, which was a bold move and even not been so perfect yet, for me proves at all that was the right decision, and of course, we did most of possible fixes and insanities on KDE 3 !!
I can tell, we sacrificed polish a kde 4 environment, today in contrib, due our heavy tasks to make KDE 3 as best as possible. I can't measure the stress of hunt and do changes like we want, and some couldn't be solved to last moments, but i can say was one of the best KDE deployments the Mandriva KDE team did ever. From the screensaver to the kicker changes to menu changes, all small patches and fixes almost impossible to be noted, but which took hours from us to find, or even touch in monster codes like kicker one, and integrate new features.
As i promised myself, the day we gone gold, would be last day i would see KDE 3 in my personal work machine, so now i'm using in production KDE 4.0.68 over 2008.1 base and i guess you know why ...
So congrats to everyone that did a wonderful job on Mandriva Spring and we finally break the curse

We implemented some very interesting features for openSUSE 11.0 to make the
installation easier and faster:

• giving it a green face
• making the configuration automatic
• switching from bzip to lzma for rpm payload
• put images of default patterns on the DVDs
• move online update to the desktop applets
• improved package management speed

Yesterday I installed 11.0 Alpha3+ (which is a snapshot of Factory burned
on DVD) and it definitely felt fast and easy. So today I decided to give
10.3 another try to measure where exactly we improved or if it's just placebo.

I let the #yast channel know my ongoing times (here only a short excerpt):
10:22 * coolo starts with a 10.3-i386
10:23 < coolo> ok, let's start.
10:29 < coolo> 6 minutes for first stage configuration
10:52 < coolo> finishing basic installation
11:06 < coolo> I'm in the 10.3 KDE online and registered
11:06 < coolo> 43 minutes all in all
11:09 < coolo> ok, on to 11.0
11:16 < coolo> starting from DVD
11:21 < coolo> first stage config done
11:25 < coolo> images deployed
11:33 < coolo> finishing basic installation
11:40 < coolo> I'm online in KDE - 24 minutes

I did not do online updates in either - that would have been incomparable, the
registration is missing from 11.0 though, this will only be done in time for
beta1. But even if you add another 2 minutes, an improvement from 43 to 26
minutes would be a very good deal to install a full blown system with 2.6 GB.

Sorry that I did not create graphical representations of the individual stages,
that will come later - and yes, the title of this blog was fixed before I did
the actual testing.

I've received 2 emails asking for more blogging and info about current klik2, especially since FOSDEM 2008.

Unfortunately, I don't have much time these weeks for 'FOSS-work', due to pressing 'work-work' duties. Since about October, I'm entangled deeply (too deep, if you ask me) in a major project that leads me to spend 5-6 days a week in Frankfurt (250 km away from home), with 12-14 hours a day on a customer site. Now compute: how much time does that leave me on evenings (in the Hotel) and weekends (at home), given that one-way travel time Stuttgart <=> Frankfurt is about 3 hours, and daily travel time inside Frankfurt is about 30 minutes?

This project takes much longer than initially thought. (Also, it involves only a very little bit of Linux, Solaris and Open Source, and much more MS Windows and proprietary software.) However, now there's the first light at the end of the tunnel. A few more weeks, and sometime mid-May my routines will be back to more normal.... *sigh*.

Anyways, while there are some more current klik2 development news, here's just one item for now: GSoC!

The klik team has submitted to become a mentoring organization for the Google Summer of Code 2008. If you are interested in some of the possible student projects, visit our GSoC idea's page.

We give a short description of each idea, as well as listing required skills and expected difficulty level to implement it, the programming language to use and some reference links to study:

• klik2 Updater
• klik2 Security Framework
• Enhancement/Replacement for fakechroot
• Packaging the klik2 client
• Porting klik2 to *BSD and Opensolaris
• Automate klik Recipe Testing
• Replacing Server-side APT with Server-side Smart

I appologize to everyone thinking WTF? at the following, but I have to blog
about it, otherwise I'll explode

This is the reference for our current payload:
-rw-r--r-- 1 coolo suse 36966400 13. Mär 09:42 coreutils-6.10.tar
8.61user 0.05system 0:08.66elapsed 99%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+11936outputs (0major+2007minor)pagefaults 0swaps
-rw-r--r-- 1 coolo suse 6110179 13. Mär 09:45 coreutils-6.10.tar.bz2.9

Then I did lzma -1 to lzma -9 and these are the numbers:

Due to too little testing, the Milestone 3 release announcement is postponed until Wednesday. It may actually happen even later, should I have no time to really do it on Wednesday evening, due to my work-work obligations.

Anyway, here is what we have planned for M3.

The FOSDEM 2008 organizers now have published their 'speakers interview' with probono and myself.

If you are interested in some background about the current klik2 development, it may be serving as a good general introduction into the concepts.

This is a screenshot of the current feedback table of our Milestone 3 testing. (Unfortunately I can't publish the URI for that table, because it would put too much load onto our web server if too many people used it).

Hence this screenshot only for now.

The goal is to fill in all the gray fields with some real results and to make most of the red fields turn into yellow or red.

probono is currently working on the new web interface for the klik server presenting klik2 applications to the end user. Unfortunately, we can't yet publish the exact URLs, since the server may not yet be prepared for even a mild version of slashdotting, and this is still very much work in progresss...

Here is the page for "gobby", one of our 15 "Milestone 3" test cases. A lot of the content of that page is dynamically created.

probono is currently working on the new web interface for the klik server presenting klik2 applications to the end user. Unfortunately, we can't yet publish the exact URLs, since the server may not yet be prepared for even a mild version of slashdotting, and this is still very much work in progresss...

Here is the page for "gobby", one of our 15 "Milestone 3" test cases. A lot of the content of that page is dynamically created.