From: Toni W. <to...@ik...> - 2004-05-31 13:02:22
|
Hello. As Gaim now supports SILC, it would be possibly a good idea to release a RPM version of Gaim that contains the SILC plugin too. :) I've packaged the required SILC library stuff to libsilc package. My graphical SILC client, Silky, depends on these packages too. I haven't tested if Gaim with SILC plugin builds against my package, hopefully someone else could do the testing. The source package is available from: ftp://ftp.sf.net/s/si/silky/libsilc-0.9.12-1.src.rpm Precompiled binaries: ftp://ftp.sf.net/s/si/silky/libsilc-0.9.12-1.i386.rpm ftp://ftp.sf.net/s/si/silky/libsilc-devel-0.9.12-1.i386.rpm Libsilc provides shared runtime libraries, and the devel package provides headers and stuff for building SILC clients. These packages are submitted to Fedora.us repository, and are in the queue currently. If Gaim's FC package maintainer is reading this, you could take a look at #1492 (bugzilla.fedora.org). -- Toni Willberg - to...@ik... - http://toniw.iki.fi/ Silky - A Gtk2 client for SILC - http://silky.sourceforge.net/ SILC - Secure Internet Live Conferencing - http://www.silcnet.org/ |
From: Tim R. <om...@ho...> - 2004-05-31 17:38:47
|
Would it be possible to build multiple binary rpms from a single source rpm? I'm pretty ignorant on how rpm works. If it's possible I would think the best thing to do would be to make gaimsilc package that depends on the libsilc library and gaim, and just has the silc prpl. That way one wouldn't have to download and install libsilc just to use the rest of Gaim, and one wouldn't have to build from source to use silc. Of course it's still extra work for those making the packages. And since I don't do that, or even know how, I'm not in a position to tell others how best to do it. But hopefully I can at least get to the heart of the matter of this thread, and this (https://sourceforge.net/forum/message.php?msg_id=2595036) one, etc. by provoking the others to respond. --Tim |
From: Toni W. <to...@ik...> - 2004-05-31 18:12:55
|
On Mon, 2004-05-31 at 20:29, Tim Ringenbach wrote: > Would it be possible to build multiple binary rpms from a single source > rpm? Yes. Fe. libsilc.rpm and libsilc-devel.rpm are both built from libsilc.src.rpm. > I'm pretty ignorant on how rpm works. If it's possible I would > think the best thing to do would be to make gaimsilc package that > depends on the libsilc library and gaim, and just has the silc prpl. Yes, this is possible, if that's the way how it's done for other add-on protocols too. > That way one wouldn't have to download and install libsilc just to use > the rest of Gaim, and one wouldn't have to build from source to use > silc. Yep. > Of course it's still extra work for those making the packages. The packagers are who are supposed to do the extra work. :> > And > since I don't do that, or even know how, I'm not in a position to tell > others how best to do it. But hopefully I can at least get to the heart > of the matter of this thread, and this > (https://sourceforge.net/forum/message.php?msg_id=2595036) one, etc. by > provoking the others to respond. -- Toni Willberg - to...@ik... - http://toniw.iki.fi/ Silky - A Gtk2 client for SILC - http://silky.sourceforge.net/ SILC - Secure Internet Live Conferencing - http://www.silcnet.org/ |
From: Stu T. <st...@no...> - 2004-05-31 19:55:01
Attachments:
gaim-0.79cvs-spec-silc.patch
|
On Mon, 2004-05-31 at 14:12, Toni Willberg wrote: > On Mon, 2004-05-31 at 20:29, Tim Ringenbach wrote: > > Would it be possible to build multiple binary rpms from a single source > > rpm? > > Yes. Fe. libsilc.rpm and libsilc-devel.rpm are both built from > libsilc.src.rpm. And of course how gaim & gaim-devel are both built from gaim.src.rpm :) > > I'm pretty ignorant on how rpm works. If it's possible I would > > think the best thing to do would be to make gaimsilc package that > > depends on the libsilc library and gaim, and just has the silc prpl. > > Yes, this is possible, if that's the way how it's done for other add-on > protocols too. SILC is the only protocol in Gaim at the moment that *depends* on 3rd party libraries, all the others are all self contained. The attached patch to gaim.spec.in will allow building the gaim .src.rpm with 'rpmbuild --rebuild --with silc gaim.src.rpm' and produce a separate binary gaim-silc.arch.rpm - only this RPM will depend on having libsilc installed. It assumes libsilc headers are installed in %{_includedir}/silc/ and libs installed in %{_libdir}/silc/ Regards, Stu. |
From: Pekka R. <pri...@ik...> - 2004-06-02 09:09:12
|
: > Yes, this is possible, if that's the way how it's done for other add-on : > protocols too. : : SILC is the only protocol in Gaim at the moment that *depends* on 3rd : party libraries, all the others are all self contained. : : The attached patch to gaim.spec.in will allow building the gaim .src.rpm : with 'rpmbuild --rebuild --with silc gaim.src.rpm' and produce a : separate binary gaim-silc.arch.rpm - only this RPM will depend on having : libsilc installed. : : It assumes libsilc headers are installed in %{_includedir}/silc/ and : libs installed in %{_libdir}/silc/ : Is that patch going into the CVS? Pekka ________________________________________________________________________ Pekka Riikonen priikone at silcnet.org Secure Internet Live Conferencing (SILC) http://silcnet.org/ |
From: Mark D. <ma...@ki...> - 2004-06-22 04:25:24
|
On Mon, 31 May 2004 15:54:26 -0400, Stu Tomlinson wrote > The attached patch to gaim.spec.in will allow building the gaim .src.rpm > with 'rpmbuild --rebuild --with silc gaim.src.rpm' and produce a > separate binary gaim-silc.arch.rpm - only this RPM will depend on having > libsilc installed. > > It assumes libsilc headers are installed in %{_includedir}/silc/ and > libs installed in %{_libdir}/silc/ Everything with this is perfect, EXCEPT: gaim-0.79cvs-0.i386.rpm also depends on libsilc, and that's bad. Specifically: [mark@diverge i386]$ rpm -qRp gaim-0.79cvs-0.i386.rpm | grep -i silc libsilc-1.0.so.2 libsilcclient-1.0.so.2 -Mark -- O O Mark Doliner \ | ma...@ki... \ | www.kingant.net "There needs to be a better word for weird." |
From: Pekka R. <pri...@ik...> - 2004-06-22 09:14:13
|
: > The attached patch to gaim.spec.in will allow building the gaim .src.rpm : > with 'rpmbuild --rebuild --with silc gaim.src.rpm' and produce a : > separate binary gaim-silc.arch.rpm - only this RPM will depend on having : > libsilc installed. : > : > It assumes libsilc headers are installed in %{_includedir}/silc/ and : > libs installed in %{_libdir}/silc/ : : Everything with this is perfect, EXCEPT: : gaim-0.79cvs-0.i386.rpm also depends on libsilc, and that's bad. Specifically: : : [mark@diverge i386]$ rpm -qRp gaim-0.79cvs-0.i386.rpm | grep -i silc : libsilc-1.0.so.2 : libsilcclient-1.0.so.2 : I guess it's then included in the gaim package instead of separate plugin. Ethan sent email yesterday that if the SILC libs are installed in your system it includes now it automatically, so isn't this what you're seeing now. Pekka ________________________________________________________________________ Pekka Riikonen priikone at silcnet.org Secure Internet Live Conferencing (SILC) http://silcnet.org/ |
From: Stu T. <st...@no...> - 2004-06-22 10:49:40
Attachments:
gaim-0.79cvs-spec-silc-take2.patch
|
On Tue, 2004-06-22 at 00:25, Mark Doliner wrote: > Everything with this is perfect, EXCEPT: > gaim-0.79cvs-0.i386.rpm also depends on libsilc, and that's bad. Specifically: > > [mark@diverge i386]$ rpm -qRp gaim-0.79cvs-0.i386.rpm | grep -i silc > libsilc-1.0.so.2 > libsilcclient-1.0.so.2 /me grumbles. Take 2 attached. This fixes the dependency problems on the main gaim package, and also corrects file ownership & permissions in the gaim-silc package which my previous patch got wrong. Regards, Stu. |
From: Mark D. <ma...@ki...> - 2004-06-24 04:47:42
|
On Tue, 22 Jun 2004 06:49:54 -0400, Stu Tomlinson wrote > On Tue, 2004-06-22 at 00:25, Mark Doliner wrote: > > Everything with this is perfect, EXCEPT: > > gaim-0.79cvs-0.i386.rpm also depends on libsilc, and that's bad. Specifically: > > > > [mark@diverge i386]$ rpm -qRp gaim-0.79cvs-0.i386.rpm | grep -i silc > > libsilc-1.0.so.2 > > libsilcclient-1.0.so.2 > > /me grumbles. > Take 2 attached. > > This fixes the dependency problems on the main gaim package, and also > corrects file ownership & permissions in the gaim-silc package which > my previous patch got wrong. > > Regards, > > Stu. I have committed this. Stu, thank you for your relentless ass-kicking, and sorry for my long round-trip time when testing this and other recent patches of yours. I'll build gaim-silc RPMs for Mandrake 9.whatever and whatever else I make, and I imagine Paco-Paco will do the same. For Mandrake... should I also provide libsilc and libsilc-devel RPMs? I haven't looked, but I wouldn't think they would be provided by the distro. -Mark -- O O Mark Doliner \ | ma...@ki... \ | www.kingant.net "There needs to be a better word for weird." |
From: Toni W. <to...@ik...> - 2004-06-24 05:29:24
|
On Thu, 2004-06-24 at 07:47, Mark Doliner wrote: > For Mandrake... should I also > provide libsilc and libsilc-devel RPMs? I haven't looked, but I wouldn't > think they would be provided by the distro. My original .spec file should be compatible with RH, Fedora, SuSe and Mandrake. It even seems to generate binaries that are work in all of distros... If there are something to be changed in the file, please mail me directly. Thanks, Toni |
From: Ethan B. <ebl...@cs...> - 2004-05-31 20:27:13
|
Tim Ringenbach spake unto us the following wisdom: > Would it be possible to build multiple binary rpms from a single source= =20 > rpm? I'm pretty ignorant on how rpm works. If it's possible I would=20 > think the best thing to do would be to make gaimsilc package that=20 > depends on the libsilc library and gaim, and just has the silc prpl.=20 > That way one wouldn't have to download and install libsilc just to use=20 > the rest of Gaim, and one wouldn't have to build from source to use=20 > silc. Of course it's still extra work for those making the packages. And= =20 > since I don't do that, or even know how, I'm not in a position to tell=20 > others how best to do it. But hopefully I can at least get to the heart= =20 > of the matter of this thread, and this=20 > (https://sourceforge.net/forum/message.php?msg_id=3D2595036) one, etc. by= =20 > provoking the others to respond. Actually, on my system I normally build against static SILC libraries anyway (I'm not sure why, this is what SILC builds by default and I haven't looked into it). This would not incur any install-time depen- dencies, so it might be a better option... Ethan --=20 The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, "On Crimes and Punishments", 1764 |
From: Pekka R. <pri...@ik...> - 2004-05-31 21:24:43
|
: > since I don't do that, or even know how, I'm not in a position to tell : > others how best to do it. But hopefully I can at least get to the heart : > of the matter of this thread, and this : > (https://sourceforge.net/forum/message.php?msg_id=2595036) one, etc. by : > provoking the others to respond. : : Actually, on my system I normally build against static SILC libraries : anyway (I'm not sure why, this is what SILC builds by default and I : haven't looked into it). This would not incur any install-time depen- : dencies, so it might be a better option... : When compiled from sources the Toolkit builds by default static libraries. Give --enable-shared to compile shared as well. For binary distribution of this kind like Gaim is I'm not sure if the static is the most appropriate. Though, personally it doesn't matter much to me which way to do it. But I would like to see the SILC prpl in binary in one way or another. For Win32 it would be nice to be one cohesive package for those Windoze users to make it as simple as possible. But I think we can make some special packages on the silcnet.org site too. Pekka ________________________________________________________________________ Pekka Riikonen priikone at silcnet.org Secure Internet Live Conferencing (SILC) http://silcnet.org/ |
From: Kevin M S. <ke...@si...> - 2004-06-01 00:03:23
|
Pekka Riikonen wrote: > When compiled from sources the Toolkit builds by default static libraries. > Give --enable-shared to compile shared as well. For binary distribution > of this kind like Gaim is I'm not sure if the static is the most > appropriate. Though, personally it doesn't matter much to me which way to > do it. But I would like to see the SILC prpl in binary in one way or > another. For Win32 it would be nice to be one cohesive package for those > Windoze users to make it as simple as possible. But I think we can make > some special packages on the silcnet.org site too. > Where Windows Gaim is concerned, we usually try to package any libraries needed with Gaim, so this would be the preferred method, and I'm sure Herman would be fine with packing a SILC library with the win32 distribution as soon as someone makes SILC build in win32. We're also going to need to provide for the sake of "build instructions" a package with the necessary SILC libraries and/or headers that people can download and place into the defined build environment to make things work. Kevin |
From: Pekka R. <pri...@ik...> - 2004-06-01 07:56:16
|
On Mon, 31 May 2004, Kevin M Stange wrote: : > another. For Win32 it would be nice to be one cohesive package for those : > Windoze users to make it as simple as possible. But I think we can make : > some special packages on the silcnet.org site too. : > : Where Windows Gaim is concerned, we usually try to package any libraries : needed with Gaim, so this would be the preferred method, and I'm sure : Herman would be fine with packing a SILC library with the win32 : distribution as soon as someone makes SILC build in win32. We're also : going to need to provide for the sake of "build instructions" a package : with the necessary SILC libraries and/or headers that people can : download and place into the defined build environment to make things work. : Yeah, that would be the best IMO. The SILC Toolkit is available from silcnet.org as pre-compiled package for Win32. It includes dynamic libraries and static libraries, which ever the developers wish to use. You can download it from: http://silcnet.org/software/download/toolkit/ The SILC Toolkit package includes MSVC++ build environment which is the one we use to build the DLLs and static libs. The package also includes full source code, and headers. The Win32 environment is located under win32/ subdirectory in the package (from root), where also the precompiled libraries exist (both Release and Debug versions). One of our developers actually compiled earlier version of Gaim with SILC for Win32 so it has been confirmed that it works on Windows. Pekka ________________________________________________________________________ Pekka Riikonen priikone at silcnet.org Secure Internet Live Conferencing (SILC) http://silcnet.org/ |
From: Toni W. <to...@ik...> - 2004-06-22 11:15:50
|
On Tue, 2004-06-22 at 13:49, Stu Tomlinson wrote: > This fixes the dependency problems on the main gaim package, and also > corrects file ownership & permissions in the gaim-silc package which my > previous patch got wrong. + %{?_with_silc:--with-silc-includes=%{_includedir}/silc} \ + %{?_with_silc:--with-silc-libs=%{_libdir}/silc} + This isn't necessarily correct, as the libdir could be fe. /usr/local/silc/lib (and no silc/ subdir after that). Ie. remove the trailing /silc and it looks better. - Toni |
From: Stu T. <st...@no...> - 2004-06-22 11:22:04
|
On Tue, 2004-06-22 at 07:15, Toni Willberg wrote: > On Tue, 2004-06-22 at 13:49, Stu Tomlinson wrote: > + > %{?_with_silc:--with-silc-includes=%{_includedir}/silc} \ > + > %{?_with_silc:--with-silc-libs=%{_libdir}/silc} > + > > This isn't necessarily correct, as the libdir could be fe. > /usr/local/silc/lib (and no silc/ subdir after that). > > Ie. remove the trailing /silc and it looks better. It may look better, but it won't work (unless we also update Gaim's ./configure). As the only RPMs I know of for silc-toolkit are the ones you provide for use with Silky, it is designed to work with them. As there is a "BuildRequires: libsilc-devel" when building with silc, then there must be *an RPM* of libsilc-devel installed, and $includir/silc & $libdir/silc are pretty much the only logical places for such RPMs to put things. Regards, Stu. |
From: Mark D. <ma...@ki...> - 2004-06-24 12:34:16
|
On Thu, 24 Jun 2004 08:29:08 +0300, Toni Willberg wrote > On Thu, 2004-06-24 at 07:47, Mark Doliner wrote: > > For Mandrake... should I also > > provide libsilc and libsilc-devel RPMs? I haven't looked, but I wouldn't > > think they would be provided by the distro. > > My original .spec file should be compatible with RH, Fedora, SuSe and > Mandrake. It even seems to generate binaries that are work in all of > distros... If there are something to be changed in the file, please mail > me directly. > > Thanks, > Toni Excellent, I guess we'll just point people to http://sourceforge.net/project/showfiles.php?group_id=86891&package_id=104581 for SILC RPMs. Let somebody know if you would rather us link to the silky homepage or something. -Mark -- O O Mark Doliner \ | ma...@ki... \ | www.kingant.net "There needs to be a better word for weird." |
From: Toni W. <to...@ik...> - 2004-06-27 16:46:27
|
On Thu, 2004-06-24 at 15:33, Mark Doliner wrote: > Excellent, I guess we'll just point people to > http://sourceforge.net/project/showfiles.php?group_id=86891&package_id=104581 > for SILC RPMs. Let somebody know if you would rather us link to the silky > homepage or something. > -Mark I'll try to move the libsilc rpms from sf.net to silcnet.org soon, lets link there instead. - Toni |