Goswin von Brederlow <[EMAIL PROTECTED]> writes: > Matthias Julius <[EMAIL PROTECTED]> writes: > >> I think aptitude uses /var/lib/apt/lists/*Packages to determine >> dependencies. How else would it know about them for packages that are >> not installed. It would need to consult *Sources to find out >> build-depends. This should not be too hard. > > That is not what I ment. When you select "install build-depends for > foobar" in aptitude it would have to somehwere record "build-depends > for foobar: manual" so it can keep all build-depends on automatic and > not remove them too early. >
Aptitude would need to keep that information at the same place it keeps the automatic flag, probably /var/lib/aptitude/pkgstates? > Hehe. No I wouldn't want to duplicate the source packages. The idea I > have in mind is to trick apt into accepting the actual source > files as debs (via the apt-get wrapper) and have the dpkg-deb wrapper > present them to dpkg in the format of debs. The DEBIAN dir would get > created on the fly and the source file itself wrapped in a tar file. > > It is a dirty hack but where else do we get to have some fun? Let me know when it works. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
