While trying to emerge gnome-2.12 it came to me that it should be alot easyer to install ~arch packages. Currently you should add all of the depencies to the package.keywords file. This can be alot of work with some packages. You could write script to make it easyer, but I think this is not a very good solution. Also when upgrading and the packages needs another keyworded package as a depency you have to add it. My solution would be to making the package.keywords and package.unmask recursive. The package that would be listed in this file would be unkeyworded and also all of it depencies wiche are still keyworded. An other file then package.keyword and unmask would have to be used to remain compatiable with the old portages. These are just some idea's. I tryed looking into the portage code to make a simple patch but it's hard to find out how to do this. Please let me know what you all think about it. Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51.22-r3 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.12-gentoo-r10 x86_64) ================================================================= System uname: 2.6.12-gentoo-r10 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.13 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [disabled] dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distcc distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.nl.gentoo.org/gentoo-portage" USE="amd64 X aac acc alsa avi bash-completion berkdb bitmap-fonts browserplugin cdr crypt cups curl dvdr eds emboss encode esd fam firefox firefox-bin font-server foomaticdb fortran gif gnome gpm gstreamer gtk gtk2 imlib ipv6 java jpeg junit kerberos ldap libwww lzw lzw-tiff mad mp3 mpeg mysql ncurses nls ogg opengl pam pdflib perl png python quicktime readline sdl server spell ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts usb userlocales vorbis xml2 xmms xpm xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
I'd nix this very fast.... It would make it almost impossible to find out what was unmasked, and therefore maybe broken, and what not
External tool to do this _maybe_, but portage isn't going to do it. Too easy for this to unmask half the tree. Everytime you sync, if portage was doing this, it would result in different keywording.
