Hi, This mail is continuation of a discussion last month on IRC on #gentoo-portage. As I think it's larger than just portage array, here it is.
I have one server dedicated for compilation (xm-compile), and many applicative servers (xmred5, lemonhead, etc). Currently I use the --buildpkg on xm-compile to build packages emergeable by --getbinpkgonly. Everything is fine except that I'm not able to --getbinpkg function of USE flags, CFLAGS, CHOST nor ACCEPT_KEYWORDS. So all packages on all servers are build in the same way with same USE. But I would like to avoid it. I have mx servers (exim) that need mysql lib, so mysql USE is there. I have mysql servers so -minimal USE is there. I don't want to install a full mysql on mx servers, I just need mysql lib. So I'd like to build custom packages for almost everything. I don't want to build packages on servers for security reasons (somes could reproach me that, but it's not the topic ;) and for a limitation of disk usage. So, I did a wrapper to emerge --buildpkg to create tbz2 with SHA1 in names function of USE, like : CHOST="x86_64-pc-linux-gnu" ACCEPT_KEYWORDS="amd64" tcpdump USE="+chroot +ipv6 -ssl -test -samba -smi" is placed under /data/pkg/amd64/x86_64-pc-linux-gnu/net-analyzer/tcpdump-4.0.1_pre20090709+2bf4bfffad82d4ae519f76770b4f7db7b4416738.tbz2 USE="+chroot +ipv6 +ssl -test +samba -smi" is placed under /data/pkg/amd64/x86_64-pc-linux-gnu/net-analyzer/tcpdump-4.0.1_pre20090709+5e099e8337e4cadfceda6ccf4c881fbb495980bd.tbz2 Like this, I can easily add on client side a portage bashrc to get the file and place it in the good place to don't have portage to download it as it would find the right file with good USE. This implies I need to emerge 1 package per 1 package which is horrible after some times. So, do you guys plan to implement a such thing ? That's one of the features that is mostly missing imho. The principal miss in on client side as I have tools to manage packages but would like to not have too much specific scripts on client side. Thanks, -- Beber
signature.asc
Description: Digital signature
