From: salsaman <sal...@xs...> - 2006-03-26 06:17:39
|
Hi, I am testing libvisual 0.4.0. First thing I noticed is there is some kind of madness with pkg-config. Now look, the idea of pkg-config is to make a package and its flags easy to find. It makes sense then to have livisual.pc. It does not make any sense to have libvisual-<version>.pc that is what pkg-config --modversion is for - to retrieve the pakage version ! What justification is there for having libvisual-<version>.pc ? It's hardly likely that a user would want to have multiple versions of libvisual on their system. Please consider moving back to libvisual.pc Also this version number madness has continued into the libraries, after installing 0.4.0 over 0.2.0 here is the mess I ended up with in /usr/lib: -rwxr-xr-x 1 root root 890 Mar 26 07:54 /usr/lib/libvisual-0.4.la* lrwxrwxrwx 1 root root 22 Mar 26 07:54 /usr/lib/libvisual-0.4.so-> libvisual-0.4.so.0.0.0* lrwxrwxrwx 1 root root 22 Mar 26 07:54 /usr/lib/libvisual-0.4.so.0 -> libvisual-0.4.so.0.0.0* -rwxr-xr-x 1 root root 689958 Mar 26 07:54 /usr/lib/libvisual-0.4.so.0.0.0* -rwxr-xr-x 1 root root 868 Feb 1 21:45 /usr/lib/libvisual.la* lrwxrwxrwx 1 root root 18 Feb 1 21:45 /usr/lib/libvisual.so -> libvisual.so.0.0.0* lrwxrwxrwx 1 root root 18 Mar 20 11:49 /usr/lib/libvisual.so.0 -> libvisual.so.0.0.0* -rwxr-xr-x 1 root root 135496 Aug 22 2005 /usr/lib/libvisual.so.0.0.0* More to follow... Salsaman http://lives.sourceforge.net |
From: Dennis S. <sy...@yo...> - 2006-03-28 07:15:51
|
Heya Salsaman, This is at all no madness, most clients are still on 0.2.0 so that is why parallel installability is needed, and also very sane. Most libraries do this by design, it was a thing we've been lacking in the past. example: lrwxrwxrwx 1 root root 21 2006-01-18 21:49 libglib-1.2.so.0 -> libglib-1.2.so.0.0.10 -rw-r--r-- 1 root root 151K 2006-01-11 12:12 libglib-1.2.so.0.0.10 -rw-r--r-- 1 root root 772K 2006-01-18 20:41 libglib-2.0.a -rw-r--r-- 1 root root 807 2006-01-18 20:41 libglib-2.0.la lrwxrwxrwx 1 root root 22 2006-01-24 16:32 libglib-2.0.so -> libglib-2.0.so.0.800.6 lrwxrwxrwx 1 root root 22 2006-01-24 16:32 libglib-2.0.so.0 -> libglib-2.0.so.0.800.6 -rw-r--r-- 1 root root 528K 2006-01-18 20:41 libglib-2.0.so.0.800.6 pkg-config: glib-2.0.pc glib.pc These are just examples, most libraries do this. We will not consider moving back to the old flawed and faulty library versioning style, also it's no problem for applications even better, you can easily select which major release you want. Also please consider a tone that is less in the style of: 'mess','madness' and 'crap'. Cheers, Dennis On Sun, 2006-03-26 at 08:31 +0200, salsaman wrote: > Hi, > I am testing libvisual 0.4.0. First thing I noticed is there is some > kind of madness with pkg-config. > > Now look, the idea of pkg-config is to make a package and its flags easy > to find. It makes sense then to have livisual.pc. > It does not make any sense to have libvisual-<version>.pc > > that is what pkg-config --modversion is for - to retrieve the pakage > version ! > > What justification is there for having libvisual-<version>.pc ? It's > hardly likely that a user would want to have multiple versions of > libvisual on their system. > > Please consider moving back to libvisual.pc > > > Also this version number madness has continued into the libraries, after > installing 0.4.0 over 0.2.0 here is the mess I ended up with in /usr/lib: > > -rwxr-xr-x 1 root root 890 Mar 26 07:54 /usr/lib/libvisual-0.4.la* > lrwxrwxrwx 1 root root 22 Mar 26 07:54 /usr/lib/libvisual-0.4.so-> > libvisual-0.4.so.0.0.0* > lrwxrwxrwx 1 root root 22 Mar 26 07:54 /usr/lib/libvisual-0.4.so.0 > -> libvisual-0.4.so.0.0.0* > -rwxr-xr-x 1 root root 689958 Mar 26 07:54 /usr/lib/libvisual-0.4.so.0.0.0* > -rwxr-xr-x 1 root root 868 Feb 1 21:45 /usr/lib/libvisual.la* > lrwxrwxrwx 1 root root 18 Feb 1 21:45 /usr/lib/libvisual.so -> > libvisual.so.0.0.0* > lrwxrwxrwx 1 root root 18 Mar 20 11:49 /usr/lib/libvisual.so.0 -> > libvisual.so.0.0.0* > -rwxr-xr-x 1 root root 135496 Aug 22 2005 /usr/lib/libvisual.so.0.0.0* > > > More to follow... > > > Salsaman > http://lives.sourceforge.net > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Libvisual-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libvisual-devel |
From: Chong K. X. <des...@ph...> - 2006-04-02 20:18:34
|
I somewhat admire synap's patience in the response he made. It's clear that you're the one who has never thought about the issue, nor have experience dealing with parallel installable libraries. But apparently, that didn't stop you from being vociferous. Next time, don't assume we're idiots. You can question nicely if you think we made a mistake. On Sun, 2006-03-26 at 08:31 +0200, salsaman wrote: > Hi, > I am testing libvisual 0.4.0. First thing I noticed is there is some=20 > kind of madness with pkg-config. >=20 > Now look, the idea of pkg-config is to make a package and its flags easy=20 > to find. It makes sense then to have livisual.pc. > It does not make any sense to have libvisual-<version>.pc >=20 > that is what pkg-config --modversion is for - to retrieve the pakage=20 > version ! >=20 > What justification is there for having libvisual-<version>.pc ? It's=20 > hardly likely that a user would want to have multiple versions of=20 > libvisual on their system. >=20 > Please consider moving back to libvisual.pc >=20 >=20 > Salsaman > http://lives.sourceforge.net >=20 --=20 Chong Kai Xiong (Descender) GPG public key: 1024D/83EC297C Key fingerprint =3D 51D6 1C5F 36C9 4428 6933 5239 6A45 502B 83EC 297C |