On Friday 01 July 2005 12:25 pm, Brian D. Harring wrote: > Currently, we pretty much leave out the big dogs of build depends from > ebuilds- basically we rely on the profile to require a suitable > toolchain. Couple of issues with this though- > > 1) Deps aren't complete for an ebuild. > 2) Merging a php or python lib that doesn't require compilation > doesn't require a full toolchain, distutils/pear or make mainly. > So autoassuming a c/c++ toolchain is required isn't accurate. > 3) For automatically handling x-compile deps, without this info bound > to an ebuild, portage will _never_ be able to know what > dependencies are x-compile targets, and what deps must be natively > merged.
so what you're proposing is that we add binutils/gcc/glibc to every package that compiles something, make to every package that uses make, sed/grep/bash/coreutils to every package which runs configure, and tar/gzip/bzip2 to every package which has a gzipped/bzipped tarball in SRC_URI ? -mike -- gentoo-dev@gentoo.org mailing list
