Greetings,
Recently I started playing a bit with building RPMs and produced rpms for: * Pidgin guifications * Pidgin plugin pack from guifications.sf.net * gnome-main-menu 0.9.8
Those can be found in my little experimental repository at http://rpm.i-nz.net . I am wondering if it is a good idea (of course if those rpms meet your standards) to get those rpms in the Community repository? I am planning on backporting and packaging gnome software every now and then when I need something in the future.
Regards.
Ivan N. Zlatev wrote:
Greetings,
Recently I started playing a bit with building RPMs and produced rpms for:
- Pidgin guifications
- Pidgin plugin pack from guifications.sf.net
- gnome-main-menu 0.9.8
Those can be found in my little experimental repository at http://rpm.i-nz.net . I am wondering if it is a good idea (of course if those rpms meet your standards) to get those rpms in the Community repository? I am planning on backporting and packaging gnome software every now and then when I need something in the future.
GNOME:Community can be your playground.
Feel free to do it for pidgin-* stuff. Guifications are in our wish list for a long time.
Pidgin itself is already there and I am working on its move to Factory.
If you have a Build Service account I can add you to a maintainers list to allow you to check packages in. You only need to write your account ID.
If you don't have, you can ask for account (process should be documented on the OpenSUS web).
gnome-main-menu should be already packaged in the GNOME:UNSTABLE project.
Pidgin itself is already there and I am working on its move to Factory.
Will you ping the list once it's in so I can disable the G:C packages?
James Ogley wrote:
Pidgin itself is already there and I am working on its move to Factory.
Will you ping the list once it's in so I can disable the G:C packages?
Yes.
FYI, I started with pidgin from GNOME:Community. It compiles OK, but did not pass several QA tests: unowned directories, files packaged multiple times, undefined C code, strict-aliasing check, bad GConf scriptlets. Some parts of the spec file looks ugly (e. g. removing $RPM_BUILD_ROOT traces).
I plan to split several plugins to a separate package (e. g. mono), so the main package will not depend on mono.
I will also evaluate possible enabling of remaining plugins.
On 5/9/07, Stanislav Brabec sbrabec@suse.cz wrote:
I plan to split several plugins to a separate package (e. g. mono), so the main package will not depend on mono.
I have to say that the mono support/bindings are far away from complete (read as in completly "broken"), so I would recommend compiling Pidgin without that support for now.
Regards.
James Ogley wrote:
Pidgin itself is already there and I am working on its move to Factory.
Will you ping the list once it's in so I can disable the G:C packages?
It's finally rebuilt in GNOME:UNSTABLE.
It's not yet in Factory. It will be checked there after Alpha4.
Now I plan to build Pidgin with SILC support and clean the package.
James, could you tell me the purpose of patches you included into gaim-unstable? Should I try to port them or drop?
James, could you tell me the purpose of patches you included into gaim-unstable? Should I try to port them or drop?
They were the patches from the openSUSE gaim package that hadn't been merged (or the functionality added) upstream.
I had an email from Martin Szulecki saying he'd ported all the patches to pidgin but I've not had time to look into it yet.
He has a source rpm containing them at http://rpm.sukimashita.com/10.2/src/pidgin-1.99.7-4.src.rpm - the keyring patch he includes appears to be the same OpenSolaris one I tried that doesn't work properly though. It's possible he's fixed it I suppose.
He also points out that gaim-encryption (do we include that? I can't remember) has been updated to pidgin-encryption.
On 5/7/07, Stanislav Brabec sbrabec@suse.cz wrote:
If you have a Build Service account I can add you to a maintainers list to allow you to check packages in. You only need to write your account ID.
If you don't have, you can ask for account (process should be documented on the OpenSUS web).
I've applied for a OBS account last week, but my account is not yet approved.
Regards.
-
Ivan N. Zlatev -
James Ogley -
Stanislav Brabec