On Thu, Mar 18, 2010 at 19:42:37 +0100, Stefano Zacchiroli wrote: > the function dep_for_me() in the Python code checks, for each build-dep, > if it is part of that list. If a build-dep is, it gets "simplified > away". In your example it is trivially the case for 'libc6-dev', which > gets removed. > Well, it should remove the whole alternative, not just the one package. > Now, as I understand it, the code which currently throws away essential > build-deps is too simple: it currently does not care about versions at > all, while it probably should. Is this the root of the problem? If it > is, there are various thoughts before fixing this naively: > > - how can add-sources.py know the version of the build-essential > packages which will be installed while actually building? > > - should it know that in the first place? > > I don't currently remember the rationale of ignoring build-essential > (were there cases where they are not installable, according to their > deps?), so I'm a bit at loss here ... > There are cases where some build-essential package is not installable if you only look at the Packages file, but where this should be ignored because build-essential packages are already installed on the buildd, so the installability of their versions in the Packages file is irrelevant. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature