Ok, put simply, the rar package basically contains binary files - which are compiled agaist libdstdc++5. these wont run without the proper dependencies. It was a choice of either adding in a manual depends, or adding in a Build-Dep for shlibs to pick up - I went for the shlibs way, as shlibs was trying to pick it up anyways, but had problems (as libstdc++6 is brought in automatically) This is basically a depends to make the binary work properly. The binary depends on it - but it isnt source code. I'm in talks with upstream - trying to get it to build with libstdc++6 ;) Anyhoo... I've added the closes to the changelog - thanks for the reminder! Would you be happier pulling it in with Depends: rather than doing it through shlibs? Laszlo Boszormenyi wrote: > Hi Martin, > > On Sun, 2006-01-22 at 12:19 +0000, Martin Meredith wrote: >> The package I've just uploaded to mentors.debian.net, [...] > Two minor problems for the first look. Please close your ITA with the > new maintainer line; close _either_ #280595 or #337940 with the new > upstream release line. Also a cosmetic one: copyright has more than one > empty line after you declare that you made your changes as well. > But why do you need libstdc++5-3.3-dev for building rar? It seems to be > building correctly without it. Anyway, by now libstdc++6-4.0-dev should > be used if it needed. But it would come in anyway due to build-essential > dependency; thus I really don't see why do you need a libstdc++ > development package.k > About unrar: I would be happier to sponsor that, because that's the way > rar can you away - rar creates only more archives. :-( > > Regards, > Laszlo/GCS
Attachment:
signature.asc
Description: PGP signature
Attachment:
signature.asc
Description: OpenPGP digital signature