On Mon, Sep 28, 2009 at 04:05:12PM +0200, Julien Cristau wrote:
> > Practically, this can work two ways: we can have edos-builddebcheck
> > query the dpkg database for installed packages (and their relationships,
> > since they are not granted to be in sync with the APT database), or we
> > can add an option pointing to a file which lists packages which are
> > known to be forcibly installed.
> Well, edos-builddebcheck doesn't run from every buildd's chroot, so the
> first option can't work.
ACK, I feared a problem of that sort ...
> The second doesn't really sound easier than adding the knowledge in
> edos-builddebcheck (and would have to be maintained somehow...)
I agree that the cost of adding the information is probably the same. At
the maintenance level however, reading the given list of packages from a
file external to edos-builddebcheck looks way more saner. Trivially: it
will enable to change the list without changing edos-builddebcheck
itself.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
