Following up some #fink musings... Background: A buildlock is implemented (in part) as an actual package that Depends on the BuildDepends of the package being built. The goal is to prevent one from removing a package that is "in use" by that build process: fink and dpkg refuse to remove the BDeps because doing so would be a dependency violation of the buildlock package.
Issue: apt (and some other front-ends) do automatic *recursive* removal (a package and everything that depends on it), which breaks the whole buildlock mechanism. That's bad. Possible solution: Make buildlock packages Essential, which prevents all parts of the debian management system from removing them unless a special flag is passed. Fink's buildlock functions would know to do this and one could manually do it if one really wanted to, but it would prevent casual/accidental removal under all circumstances. Any thoughts about this solution, or any better ideas? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
