> What about fixing the fink dep engine, so that BuildDependsOnly > packages may depend on other BuildDependsOnly, and then a kde packahe > could BuildDepend on kdelibs3-dev and a few other -dev packages it > needs, and fink will make sure everything needed is there; fink would > need to recursively go through the depends... > > - -chris zubrzycki
When you say that they may "depend on" do you mean to use the Depends field? That doesn't work, for the following reason. The value in the Depends field is written into the .deb file and is then used by dpkg/apt-get. You'll never be able to swap back and forth between -dev packages if any of those -dev packages have things which Depend on them. Or did you mean to use the BuildDepends field? That doesn't work either, because once a package has been built, fink ignores the BuildDepends field. Or maybe did you mean to use the BuildDepends field, but change fink's behavior so that when building X, if X Depends (or BuildDepends) on Y, and Y BuildDepends on Z, then Z must be installed when building X? That's a very radical change, and might have other bad effects... at the very least, it would make the process of compiling packages much longer and more complicated than it already is. -- Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
