Re: [Cooker] pkgconfig not required by -devel
Guillaume Rousse wrote: Ainsi parlait Michael Scherer : i suggest the last solution, but, maybe someone see a problem ? Yes, coherency with other development tools. How many packages really requires autoconf/automake ? I guess less than 1%. However, autoconf/automake are rpm-build dependencies. Here we have more packages requiring what appears some new build tool, and we are gonna add it as an explicit require for each of them. This is plainly silly. If you're going to do it manually, like we are doing right now, *then* it's silly. If you're going to do it automatically, I have less issues with it. I think it's ellegant not to let rpm-build require all the build tools, otherwise rpm-build will become something like basesystem. Perhaps introducing circular dependencies, etc. Doing it with a find-requires script is fine. Stefan smime.p7s Description: S/MIME Cryptographic Signature
Re: [Cooker] pkgconfig not required by -devel
On Thursday 04 September 2003 00:32, Guillaume Rousse wrote: Ainsi parlait Michael Scherer : i suggest the last solution, but, maybe someone see a problem ? Yes, coherency with other development tools. How many packages really requires autoconf/automake ? I guess less than 1%. However, autoconf/automake are rpm-build dependencies. Here we have more packages requiring what appears some new build tool, and we are gonna add it as an explicit require for each of them. This is plainly silly. this will affect maybe 10 packages, which is not too much. i guess that only 10 packages, because nobody see the problem until now. this 10 package will be used to : - build rpm, and it will use pkgconfig, because of autoconf, most of the time. - build from source, and it will use pkgconfig, for configure script, because library authors put pkgconfig in their macros. - develop a software, which means that people will have to figure what are the good argument for gcc, and this is where they will use pkgconfig. I guess that documentation will also say to use pkgconfig. but, of course, it can be used without it. autoconf/automake is only used when developping a application, and when we patch a configure script for rpm building. Patching a script to suit our needs is almost the same as developping a application. That's why packages should not requires autotools. Most of the time, people don't need it. pkgconfig is different, because, most of the time, people will need it for a proper use of the library ( -devel rpm of the library ). I do not say to add pkgconfig requires on each library, but only to the ones that have almost 90% chances of using it. -- Michal Scherer
Re: [Cooker] pkgconfig not required by -devel
On Tue, Sep 02, 2003 at 10:11:36AM +0200, Guillaume Rousse wrote: It is still not a good idea to add as buildrequires it to a gazillion spec, either manually or automatically. Just adding rpm-build requires would be more consistent with current solution used with other build tools. AFAIK, nothing buildrequires autoconf, automake, gcc, they are considered as implicit build dependencies. All kinds of packages have buildrequires on autoconf, automake, or gcc. Though they all need specific versions. Given the recent version issues with autoconf and automake this is pretty common now for packages to need to specify that they need a particular version. -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org What upsets me is not that you lied to me, but that from now on I can no longer believe you. -- Nietzsche
Re: [Cooker] pkgconfig not required by -devel
Ainsi parlait Ben Reser : On Tue, Sep 02, 2003 at 10:11:36AM +0200, Guillaume Rousse wrote: It is still not a good idea to add as buildrequires it to a gazillion spec, either manually or automatically. Just adding rpm-build requires would be more consistent with current solution used with other build tools. AFAIK, nothing buildrequires autoconf, automake, gcc, they are considered as implicit build dependencies. All kinds of packages have buildrequires on autoconf, automake, or gcc. Though they all need specific versions. Given the recent version issues with autoconf and automake this is pretty common now for packages to need to specify that they need a particular version. Only when this is not the default version. When old autoconf/automake will get deprecated, i guess new versions will replace them in rpm-build dependencies, and current behaviour will get reversed. -- If enough data are collected, anything may be proven by statistical methods. -- Williams and Holland's Law
Re: [Cooker] pkgconfig not required by -devel
On Tuesday 02 September 2003 08:42, Michael Scherer wrote:
The patch is not perfect. If applied right now,linphone would
requires pkgconfig, which is useless.
So, what i propose is to add pkgconfig as a requires if :
- a file is dropped in /usr/lib/pkgconfig
and if
- a file is dropped in /usr/share/aclocal and this file test the
presence of pkg-config. It should be engouh to grep
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
in the file.
here is new patch, that implement what i have explained.
right now, as stefan stated , we have 3 solutions.
adding pkgconfig to rpm-build.
this will solve the problem for rpm building without needing to add
dependancy to all rpm.
but people using libfoo-devel, who use pkgconfig for ./configure script
will have to download it afterward. And, i do not think this is clan.
adding pkgconfig to each library
this is also bad because it would be added by hand. this is error prone,
and almost as bad as current solution. But this would solve the problem
of ./configure. I guess a rpmlint warning ( pc-files-without-pkgrequire
) would be enough for this one.
using the patch and automaticaly adding it to the package that need it
this would only add pkgconfig for library that really use it when
aclocal is used, and is automated, so no need to change library, just
rebuild them.
all file dropped in /usr/share/aclocal are included in ./configure
script whan aclocal is used, so, if the file check pkgconfig existence,
with a macro, it mean that all configure script trying to detect this
library will use pkgconfig, and so it is good to add it as requires.
i suggest the last solution, but, maybe someone see a problem ?
if not, i will submit a bugreport during the weekend.
--
Mickal Scherer
--- find-requires.bak 2003-09-01 09:49:23.0 +0200
+++ find-requires 2003-09-03 20:42:35.0 +0200
@@ -165,6 +165,13 @@
echo $tcllist | tr '[:blank:]' \\n | /usr/lib/rpm/tcl.req | sort -u
#
+# --- pkgconfig .pc files
+( echo $filelist | tr '[:blank:]' '\n' | grep -q '/usr/lib/pkgconfig/' )
+( aclocal_files=`echo $filelist | tr '[:blank:]' '\n' | grep '/usr/share/aclocal/'`;
+[ -n $aclocal_files ] grep -q 'AC_PATH_PROG(PKG_CONFIG, pkg-config,' $aclocal_files 2/dev/null echo 'pkgconfig'
+)
+
+#
# --- .so files.
for i in `echo $filelist | tr '[:blank:]' \n | egrep (/usr(/X11R6)?)?/lib(|64)/[^/]+\.so$`; do
objd=`objdump -p ${i} | grep SONAME`
Re: [Cooker] pkgconfig not required by -devel
[..] using the patch and automaticaly adding it to the package that need it this would only add pkgconfig for library that really use it when aclocal is used, and is automated, so no need to change library, just rebuild them. all file dropped in /usr/share/aclocal are included in ./configure script whan aclocal is used, so, if the file check pkgconfig existence, with a macro, it mean that all configure script trying to detect this library will use pkgconfig, and so it is good to add it as requires. i suggest the last solution, but, maybe someone see a problem ? if not, i will submit a bugreport during the weekend. You have my support. Stefan smime.p7s Description: S/MIME Cryptographic Signature
Re: [Cooker] pkgconfig not required by -devel
Ainsi parlait Michael Scherer : i suggest the last solution, but, maybe someone see a problem ? Yes, coherency with other development tools. How many packages really requires autoconf/automake ? I guess less than 1%. However, autoconf/automake are rpm-build dependencies. Here we have more packages requiring what appears some new build tool, and we are gonna add it as an explicit require for each of them. This is plainly silly. BTW, i was checking dependencies, rpm depends on make. Is this normal ? -- Guillaume Rousse Love is the triumph of imagination over intelligence -- Murphy's Laws on Sex n36
Re: [Cooker] pkgconfig not required by -devel
On 2003-09-04(Thu) 00:32:50 +0200, Guillaume Rousse wrote: Ainsi parlait Michael Scherer : i suggest the last solution, but, maybe someone see a problem ? Yes, coherency with other development tools. How many packages really requires autoconf/automake ? I guess less than 1%. However, autoconf/automake are rpm-build dependencies. Here we have more packages requiring what appears some new build tool, and we are gonna add it as an explicit require for each of them. This is plainly silly. You can bump that number to 99% as well by adding patches to packages. People are talking about how widespread some tools are needed, and certainly autotools/libtool are the most prominent members, while some others are not. If missing some tools will make MANY packagers' life worse, then certainly it's worthy to add that to rpm-build dependency. I think pkgconfig is almost there, but not yet. Abel BTW, i was checking dependencies, rpm depends on make. Is this normal ? -- Guillaume Rousse Love is the triumph of imagination over intelligence -- Murphy's Laws on Sex n36 -- Abel Cheung Linux counter #256983 | http://counter.li.org GPG Key: (0xC67186FF) | http://deaddog.org/gpg.asc Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF pgp0.pgp Description: PGP signature
Re: [Cooker] pkgconfig not required by -devel
On Monday 01 September 2003 21:16, Guillaume Rousse wrote: Ainsi parlait Oden Eriksson : I agree, rpm-devel should require pkgconfig. Same for me. That's silly to add it to all packages individually. But some package use pkgconfig in their autoconf macro, as a grep pkg /usr/share/aclocal * will show you. -- Mickaël Scherer
Re: [Cooker] pkgconfig not required by -devel
On 2003-09-01(Mon) 22:17:08 +0200, Michael Scherer wrote: On Monday 01 September 2003 21:16, Guillaume Rousse wrote: Ainsi parlait Oden Eriksson : I agree, rpm-devel should require pkgconfig. Same for me. That's silly to add it to all packages individually. But some package use pkgconfig in their autoconf macro, as a grep pkg /usr/share/aclocal * I think you mean grep PKG_ /usr/share/aclocal/* instead? Anyway, I'm eager to see your patch against find-requires go into rpm package, that's a much more automated solution. Abel will show you. -- Mickal Scherer -- Abel Cheung Linux counter #256983 | http://counter.li.org GPG Key: (0xC67186FF) | http://deaddog.org/gpg.asc Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF pgp0.pgp Description: PGP signature
Re: [Cooker] pkgconfig not required by -devel
On Monday 01 September 2003 23:31, Abel Cheung wrote: On 2003-09-01(Mon) 22:29:52 +0200, Stefan van der Eijk wrote: I agree, rpm-devel should require pkgconfig. Same for me. That's silly to add it to all packages individually. So..., what do you all suggest? File a bugreport or bug the rpm package maintainer? I personally think this solution would benefit the most... I guess there are 3 options: - add it as a Requires to rpm-build (not rpm-devel!) It is no really mandatory to use it for rpm building, only for some packages, so, there is no need to a requires for some packages. - add some functionality to the find-requires script - hunt down the packages and add it to the spec file Michael has already done the 2nd option as a patch to find-requires, posted in cooker. The patch is not perfect. If applied right now,linphone would requires pkgconfig, which is useless. So, what i propose is to add pkgconfig as a requires if : - a file is dropped in /usr/lib/pkgconfig and if - a file is dropped in /usr/share/aclocal and this file test the presence of pkg-config. It should be engouh to grep AC_PATH_PROG(PKG_CONFIG, pkg-config, no) in the file. -- Michal Scherer
Re: [Cooker] pkgconfig not required by -devel
Ainsi parlait Abel Cheung : Anyway, I'm eager to see your patch against find-requires go into rpm package, that's a much more automated solution. It is still not a good idea to add as buildrequires it to a gazillion spec, either manually or automatically. Just adding rpm-build requires would be more consistent with current solution used with other build tools. AFAIK, nothing buildrequires autoconf, automake, gcc, they are considered as implicit build dependencies. -- If your advance is going well, you are walking into an ambush -- Murphy's Military Laws n6
Re: [Cooker] pkgconfig not required by -devel
On 2003-09-02(Tue) 10:11:36 +0200, Guillaume Rousse wrote: Ainsi parlait Abel Cheung : Anyway, I'm eager to see your patch against find-requires go into rpm package, that's a much more automated solution. It is still not a good idea to add as buildrequires it to a gazillion spec, either manually or automatically. Just adding rpm-build requires would be more consistent with current solution used with other build tools. AFAIK, nothing buildrequires autoconf, automake, gcc, they are considered as implicit build dependencies. I don't think rpm-build is very appropriate as a kitchen sink. For autoconf, automake, gcc etc, since they are so vital (a large percentage of package will fail to build without them), they are good candidate to at least create a working build system containing basic requirements for development. But I don't think pkgconfig is in such a vital position yet (comparing to libtool, autotools etc). Abel -- If your advance is going well, you are walking into an ambush -- Murphy's Military Laws n6 -- Abel Cheung Linux counter #256983 | http://counter.li.org GPG Key: (0xC67186FF) | http://deaddog.org/gpg.asc Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF pgp0.pgp Description: PGP signature
Re: [Cooker] pkgconfig not required by -devel
On 2003-08-31(Sun) 22:16:14 +0200, Michael Scherer wrote:
http://eijk.homelinux.org/build/contrib/i586/problem/ices-0.3-2mdk
the compilation stopped when configure tried to detect libshout3-devel,
listed as buildrequires. It stopped because pkgconfig was not found.
libshout3-devel should require pkgconfig, since it is needed for the
proper auto detection of the include.
there is a lot of package who drop a file in /usr/lib/pkgconfig/ without
having a requires on pkgconfig.
Yup, most of them should be fixed. Probably it's because most
developers/packagers have already installed pkgconfig so that nobody
notice it.
this script [1] gives most of the package who misses the requires on
pkgconfig [2].
Am i wrong when i say they should be fixed ?
Because there is a lot of wrong requires, i may have missed a detail
Can mostly be sure that all -devel below needs that dependency. Is the
list below complete?
Some of the packages are not -devel library, i guess they should be
fixed, because pkgconfig files belong to the -devel.
And some are not library, such as linphone, who does not provides any
include or libray, so i guess there is a problem.
Not quite sure. For some .pc files, such as rhythmbox.pc, there's almost
no info here. The keyword is almost -- you can still, for example,
retreive path info from it:
[EMAIL PROTECTED] root]# pkg-config --variable=idldir rhythmbox
/usr/share/idl
But I have no idea whether it's internally used by software, or just
plain dumb file that can be killed.
Abel
[1]
for i in `urpmf '/usr/lib/pkgconfig/' | awk -F: '{print $1}' | sort |
uniq `;
do
if ! urpmq -d $i | grep -q pkgconfig ; then
echo $i ;
fi;
done;
[2]
autotrace
epiphany-devel
gdesklets
gedit
gkrellm-devel
gnome-mime-data
gnome-python
gnome-system-tools
gok
gretl
gstreamer-python
gtk-doc
gtk-engines2
gtkmathview
ImageMagick
libaiksaurus-1.0_0-devel
libalsa2-devel
libalsaplayer0-devel
libaudiofile0-devel
libavifile0.7-devel
libdia-newcanvas0
libdirectfb0.9_18-devel
libebg1
libecore0
libedb1
libeet0
libefs1-devel
libesound0-devel
libevas1
libexif9-devel
libflatzebra0.1
libfontconfig1-devel
libgmime2.0-devel
libgnokii0
libgphoto2-devel
libgsl0-devel
libgtkglarea2.0
libgtksharpglue-devel
libladcca1-devel
liblrdf0-devel
libmnote7-devel
libmpeg2dec0-devel
libmusicbrainz2-devel
libneon0.24-devel
libnspr4-devel
libnss3-devel
libogre0-devel
libopenbabel0-devel
libopenssl0.9.7-devel
libots-1_0-devel
libparagui1.0-devel
libpng3-devel
libscaffold-1_0-devel
libshout3-devel
libsmi2-devel
libsqlite0-devel
libstartup-notification-1_0-devel
libticables3-devel
libticalcs4-devel
libtifiles0-devel
libtre3-devel
libuser1-devel
libxfree86-devel
libxine1-devel
libxml++10-devel
libxml1-devel
libxml2-devel
libxslt1-devel
linphone
mozilla-devel
mozilla-firebird-devel
pstoedit
pyorbit-devel
rhythmbox
spirit
streamtuner-devel
zziplib0-devel
--
Mickal Scherer
--
Abel Cheung
Linux counter #256983 | http://counter.li.org
GPG Key: (0xC67186FF) | http://deaddog.org/gpg.asc
Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF
pgp0.pgp
Description: PGP signature
Re: [Cooker] pkgconfig not required by -devel
Michael,
Would you consider making this into a find-requires script? In that case
the dependencies won't need to be added manually.
regards,
Stefan
Hi.
will trying to fix buildrequires, i have come on this one
http://eijk.homelinux.org/build/contrib/i586/problem/ices-0.3-2mdk
the compilation stopped when configure tried to detect libshout3-devel,
listed as buildrequires. It stopped because pkgconfig was not found.
libshout3-devel should require pkgconfig, since it is needed for the
proper auto detection of the include.
there is a lot of package who drop a file in /usr/lib/pkgconfig/ without
having a requires on pkgconfig.
this script [1] gives most of the package who misses the requires on
pkgconfig [2].
Am i wrong when i say they should be fixed ?
Because there is a lot of wrong requires, i may have missed a detail
Some of the packages are not -devel library, i guess they should be
fixed, because pkgconfig files belong to the -devel.
And some are not library, such as linphone, who does not provides any
include or libray, so i guess there is a problem.
[1]
for i in `urpmf '/usr/lib/pkgconfig/' | awk -F: '{print $1}' | sort |
uniq `;
do
if ! urpmq -d $i | grep -q pkgconfig ; then
echo $i ;
fi;
done;
[2]
autotrace
epiphany-devel
gdesklets
gedit
gkrellm-devel
gnome-mime-data
gnome-python
gnome-system-tools
gok
gretl
gstreamer-python
gtk-doc
gtk-engines2
gtkmathview
ImageMagick
libaiksaurus-1.0_0-devel
libalsa2-devel
libalsaplayer0-devel
libaudiofile0-devel
libavifile0.7-devel
libdia-newcanvas0
libdirectfb0.9_18-devel
libebg1
libecore0
libedb1
libeet0
libefs1-devel
libesound0-devel
libevas1
libexif9-devel
libflatzebra0.1
libfontconfig1-devel
libgmime2.0-devel
libgnokii0
libgphoto2-devel
libgsl0-devel
libgtkglarea2.0
libgtksharpglue-devel
libladcca1-devel
liblrdf0-devel
libmnote7-devel
libmpeg2dec0-devel
libmusicbrainz2-devel
libneon0.24-devel
libnspr4-devel
libnss3-devel
libogre0-devel
libopenbabel0-devel
libopenssl0.9.7-devel
libots-1_0-devel
libparagui1.0-devel
libpng3-devel
libscaffold-1_0-devel
libshout3-devel
libsmi2-devel
libsqlite0-devel
libstartup-notification-1_0-devel
libticables3-devel
libticalcs4-devel
libtifiles0-devel
libtre3-devel
libuser1-devel
libxfree86-devel
libxine1-devel
libxml++10-devel
libxml1-devel
libxml2-devel
libxslt1-devel
linphone
mozilla-devel
mozilla-firebird-devel
pstoedit
pyorbit-devel
rhythmbox
spirit
streamtuner-devel
zziplib0-devel
smime.p7s
Description: S/MIME Cryptographic Signature
Re: [Cooker] pkgconfig not required by -devel
On Sun, Aug 31, 2003 at 10:16:14PM +0200, Michael Scherer wrote: there is a lot of package who drop a file in /usr/lib/pkgconfig/ without having a requires on pkgconfig. libsqlite0-devel for this one at least pkgconfig is not needed for building stuff with linsqlite, the file is there as a convenience for pkgconfig users, so should it require pkgconfig or would it be better having /usr/lib/pkgconfig/ part of filesystem rpm or similar. probably pkgconfig should be required only if the configure scripts needs it for building. regards, L. -- Luca Berra -- [EMAIL PROTECTED] Communication Media Services S.r.l. /\ \ / ASCII RIBBON CAMPAIGN XAGAINST HTML MAIL / \
Re: [Cooker] pkgconfig not required by -devel
On Monday 01 September 2003 07:54, Stefan van der Eijk wrote:
Michael,
Would you consider making this into a find-requires script? In that
case the dependencies won't need to be added manually.
done.
--
Mickaël Scherer
--- find-requires.bak 2003-09-01 09:49:23.0 +0200
+++ find-requires 2003-09-01 10:52:13.0 +0200
@@ -165,6 +165,10 @@
echo $tcllist | tr '[:blank:]' \\n | /usr/lib/rpm/tcl.req | sort -u
#
+# --- pkgconfig .pc files
+( echo $filelist | tr '[:blank:]' \\n | grep -q '/usr/lib/pkgconfig/' ) echo 'pkgconfig'
+
+#
# --- .so files.
for i in `echo $filelist | tr '[:blank:]' \n | egrep (/usr(/X11R6)?)?/lib(|64)/[^/]+\.so$`; do
objd=`objdump -p ${i} | grep SONAME`
Re: [Cooker] pkgconfig not required by -devel
måndagen den 1 september 2003 08.26 skrev Luca Berra: On Sun, Aug 31, 2003 at 10:16:14PM +0200, Michael Scherer wrote: there is a lot of package who drop a file in /usr/lib/pkgconfig/ without having a requires on pkgconfig. libsqlite0-devel for this one at least pkgconfig is not needed for building stuff with linsqlite, the file is there as a convenience for pkgconfig users, so should it require pkgconfig or would it be better having /usr/lib/pkgconfig/ part of filesystem rpm or similar. probably pkgconfig should be required only if the configure scripts needs it for building. I agree, rpm-devel should require pkgconfig. -- Regards // Oden Eriksson, Deserve-IT.com
Re: [Cooker] pkgconfig not required by -devel
Oden Eriksson wrote: måndagen den 1 september 2003 21.16 skrev Guillaume Rousse: Ainsi parlait Oden Eriksson : I agree, rpm-devel should require pkgconfig. Same for me. That's silly to add it to all packages individually. So..., what do you all suggest? File a bugreport or bug the rpm package maintainer? I personally think this solution would benefit the most... I guess there are 3 options: - add it as a Requires to rpm-build (not rpm-devel!) - add some functionality to the find-requires script - hunt down the packages and add it to the spec file Stefan smime.p7s Description: S/MIME Cryptographic Signature
Re: [Cooker] pkgconfig not required by -devel
måndagen den 1 september 2003 21.16 skrev Guillaume Rousse: Ainsi parlait Oden Eriksson : I agree, rpm-devel should require pkgconfig. Same for me. That's silly to add it to all packages individually. So..., what do you all suggest? File a bugreport or bug the rpm package maintainer? I personally think this solution would benefit the most...
Re: [Cooker] pkgconfig not required by -devel
On 2003-09-01(Mon) 22:29:52 +0200, Stefan van der Eijk wrote: I agree, rpm-devel should require pkgconfig. Same for me. That's silly to add it to all packages individually. So..., what do you all suggest? File a bugreport or bug the rpm package maintainer? I personally think this solution would benefit the most... I guess there are 3 options: - add it as a Requires to rpm-build (not rpm-devel!) - add some functionality to the find-requires script - hunt down the packages and add it to the spec file Michael has already done the 2nd option as a patch to find-requires, posted in cooker. Abel Stefan -- Abel Cheung Linux counter #256983 | http://counter.li.org GPG Key: (0xC67186FF) | http://deaddog.org/gpg.asc Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF pgp0.pgp Description: PGP signature
[Cooker] pkgconfig not required by -devel
Hi.
will trying to fix buildrequires, i have come on this one
http://eijk.homelinux.org/build/contrib/i586/problem/ices-0.3-2mdk
the compilation stopped when configure tried to detect libshout3-devel,
listed as buildrequires. It stopped because pkgconfig was not found.
libshout3-devel should require pkgconfig, since it is needed for the
proper auto detection of the include.
there is a lot of package who drop a file in /usr/lib/pkgconfig/ without
having a requires on pkgconfig.
this script [1] gives most of the package who misses the requires on
pkgconfig [2].
Am i wrong when i say they should be fixed ?
Because there is a lot of wrong requires, i may have missed a detail
Some of the packages are not -devel library, i guess they should be
fixed, because pkgconfig files belong to the -devel.
And some are not library, such as linphone, who does not provides any
include or libray, so i guess there is a problem.
[1]
for i in `urpmf '/usr/lib/pkgconfig/' | awk -F: '{print $1}' | sort |
uniq `;
do
if ! urpmq -d $i | grep -q pkgconfig ; then
echo $i ;
fi;
done;
[2]
autotrace
epiphany-devel
gdesklets
gedit
gkrellm-devel
gnome-mime-data
gnome-python
gnome-system-tools
gok
gretl
gstreamer-python
gtk-doc
gtk-engines2
gtkmathview
ImageMagick
libaiksaurus-1.0_0-devel
libalsa2-devel
libalsaplayer0-devel
libaudiofile0-devel
libavifile0.7-devel
libdia-newcanvas0
libdirectfb0.9_18-devel
libebg1
libecore0
libedb1
libeet0
libefs1-devel
libesound0-devel
libevas1
libexif9-devel
libflatzebra0.1
libfontconfig1-devel
libgmime2.0-devel
libgnokii0
libgphoto2-devel
libgsl0-devel
libgtkglarea2.0
libgtksharpglue-devel
libladcca1-devel
liblrdf0-devel
libmnote7-devel
libmpeg2dec0-devel
libmusicbrainz2-devel
libneon0.24-devel
libnspr4-devel
libnss3-devel
libogre0-devel
libopenbabel0-devel
libopenssl0.9.7-devel
libots-1_0-devel
libparagui1.0-devel
libpng3-devel
libscaffold-1_0-devel
libshout3-devel
libsmi2-devel
libsqlite0-devel
libstartup-notification-1_0-devel
libticables3-devel
libticalcs4-devel
libtifiles0-devel
libtre3-devel
libuser1-devel
libxfree86-devel
libxine1-devel
libxml++10-devel
libxml1-devel
libxml2-devel
libxslt1-devel
linphone
mozilla-devel
mozilla-firebird-devel
pstoedit
pyorbit-devel
rhythmbox
spirit
streamtuner-devel
zziplib0-devel
--
Mickaël Scherer
