[opensuse-factory] Akiirc Aki a IRC Client for massive ways of usage
Hi everyone, I've been working now for several weeks with a developer that is creating a really interesting program for the desktop that could be used in the future for plugins (amarok , KDEVELOP) and plasmoids. The application is Aki. Its an IRC Client that ships a library for a lot of use cases in other programs and even a plasmoid. I've decided to start packagin this Applicaton for opensuse and also created a project on my build service home directory already. The only thing that keeps me from a first time packaging it is the spec file. I've experimented with packages before on debian and found it a nice opportunity to start packaging for opensuse. I really don't havve much of an Idea what I have to put all into these specfiles and how to do that right so that the buildservice can package it for other Distros too. But I would like to tell you a little more about the application/library first. In its very yet basic way it is a good IRC client and by time could be even a replcement for konversation also the underlying api is well written and could be extensified so that even programs such as amarok or KDevlop can have a use of it. The Idea behind that is really simple. For example you like the musicplayer amarok and music in generall is a great hobby for you. So why not use the akiirc library for writing a little plugin that enables an IRC client in amarok. This way you could enjoy your daily dose of music and your favourite musicplayer right away. The usecase for KDevelop , I think , is even greater as you could implement the Irc client as another tab or something like this and work on a codebase that is provided by one user(being the host) or a group work that could be easiely edited this way in the group so that everybody has something from this virtual developersprint. This could even be a nice thing as it can be used as a collaborative way of debugging and increase this way the development speed of projects and bring the alltogether group closer together. So now to provide these things I would like you to help me maintain and build these packages. I will probably just need a first start example as I cant find a really good intro to this. Sincerely Andreas Marschke. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2009-06-25 01:27:40 +0200, Andreas Marschke wrote:
I've been working now for several weeks with a developer that is creating a really interesting program for the desktop that could be used in the future for plugins (amarok , KDEVELOP) and plasmoids.
The application is Aki. Its an IRC Client that ships a library for a lot of use cases in other programs and even a plasmoid. I've decided to start packagin this Applicaton for opensuse and also created a project on my build service home directory already. The only thing that keeps me from a first time packaging it is the spec file.
I've experimented with packages before on debian and found it a nice opportunity to start packaging for opensuse. I really don't havve much of an Idea what I have to put all into these specfiles and how to do that right so that the buildservice can package it for other Distros too.
But I would like to tell you a little more about the application/library first. In its very yet basic way it is a good IRC client and by time could be even a replcement for konversation also the underlying api is well written and could be extensified so that even programs such as amarok or KDevlop can have a use of it.
The Idea behind that is really simple. For example you like the musicplayer amarok and music in generall is a great hobby for you. So why not use the akiirc library for writing a little plugin that enables an IRC client in amarok. This way you could enjoy your daily dose of music and your favourite musicplayer right away. The usecase for KDevelop , I think , is even greater as you could implement the Irc client as another tab or something like this and work on a codebase that is provided by one user(being the host) or a group work that could be easiely edited this way in the group so that everybody has something from this virtual developersprint. This could even be a nice thing as it can be used as a collaborative way of debugging and increase this way the development speed of projects and bring the alltogether group closer together.
So now to provide these things I would like you to help me maintain and build these packages. I will probably just need a first start example as I cant find a really good intro to this.
packaging tutorials are easier done on irc then on mailinglists. so stop by at #opensuse-buildservice. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 25 of June 2009, Andreas Marschke wrote:
Hi everyone,
I've been working now for several weeks with a developer that is creating a really interesting program for the desktop that could be used in the future for plugins (amarok , KDEVELOP) and plasmoids.
The application is Aki. Its an IRC Client that ships a library for a lot of use cases in other programs and even a plasmoid. I've decided to start packagin this Applicaton for opensuse and also created a project on my build service home directory already. The only thing that keeps me from a first time packaging it is the spec file.
I've experimented with packages before on debian and found it a nice opportunity to start packaging for opensuse. I really don't havve much of an Idea what I have to put all into these specfiles and how to do that right so that the buildservice can package it for other Distros too.
Incidentally I've been recently working on making it easily possible to build KDE4 applications in the buildservice for all the distributions that are supported. I have several simple packages in home:llunak:kde that build with a relatively simple .spec file for openSUSE, Fedora and Mandriva. It is still work in progress and will probably still take a little time, given that Akademy is getting very near, so I cannot give you a nice howto for that now. Since you say you have experience with packaging for Debian, and I still struggle with making this ready also for Debian/Kubuntu, if you could point me to some usable 'Debian/Kubuntu KDE apps packaging for dummies' guide, that could save me time and get it ready sooner.
So now to provide these things I would like you to help me maintain and build these packages. I will probably just need a first start example as I cant find a really good intro to this.
http://en.opensuse.org/KDE/Packaging/Cookbook could be a good starting point. You could also have a look at the packages in home:llunak:kde, building for non-openSUSE is done by configuring build repositories to hide differences by mapping and that's not really done yet, but they could be enough as a template for building for openSUSE. The wiki at http://en.opensuse.org has also other information about .spec files and building, and you could stop by in #opensuse-kde , maybe there would be somebody to help you. -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak@suse.cz , l.lunak@kde.org Lihovarska 1060/12 tel: +420 284 028 972 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
It is still work in progress and will probably still take a little time, given that Akademy is getting very near, so I cannot give you a nice howto for that now. Since you say you have experience with packaging for Debian, and I still struggle with making this ready also for Debian/Kubuntu, if you could point me to some usable 'Debian/Kubuntu KDE apps packaging for dummies' guide, that could save me time and get it ready sooner.
I had just a small package that hadn't much of dependencies. But I walked the way with the debian-developers-refrence. Wasn't that bad for a work of say 2-3 days ... You can get the reference as a package on your machine or read it online here: http://www.debian.org/doc/developers-reference/ Just go with it its really not hard. :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Andreas Marschke -
Lubos Lunak -
Marcus Rueckert