[ CC'ing the ICU maintainer for completeness, but I think this report could be closed outright, it's bogus imho ]
Hi, On Fri, Aug 14, 2009 at 03:34:24PM -0400, K.S. Bhaskar wrote: > I have filed an intention to package GT.M, which depends on libicu. > Right now, I have to create a dependency libicu36|libicu38|libicu40, > etc. It would be much easier for me if there were a meta-package No, you have to create a dependency on whatever is correct (ie. what you build it with) and what is in the distribution you are packaging it for. I don't really believe that your package does find out on the fly which ICU to use, and if it uses libicu.so there's already libicu-dev which *has* a version-independent package name. Of course, if your package has a magic to find out whether it should open libicu.so.36 etc. nevermind, but that sounds scary. > libicu. I could then create a dependency on libicu and ensure that > the version is greater than 3.6. This sounds broken. That the icu packages differ in package name in different versions is for reasons (-> SONAME). > -- System Information: > Debian Release: 5.0 > APT prefers jaunty-updates > APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500, > 'jaunty-backports'), (500, 'jaunty') > Architecture: amd64 (x86_64) No comment. Grüße/Regards, Rene -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' r...@debian.org | GnuPG-Key ID: D03E3E70 `- Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70 -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
