I've talked yesterday to an Developer why not setting up BINARY-package-Hosts
for packages created with the quickpkg command. If I understand him right your
problems are the use-flags. But whats about the idea of :
-generating the package without any use-flag set and some default CFLAGS
-runing quickpkg for that ebuild
-remerging it with an useflag set and running quickpkg after that
-building a patch-file for the "NO-Useflag-set-tbz2"-file and the "Useflag-set-
-continue with the next use-flag... and so on.
So u just need to host the "NO-Useflag-set-tbz2" and the patch-files.
I would realy enjoy such a feature for just testing a big package and don't
wanne to wait a couple of hours.
Is this possible?
Steps to Reproduce:
1.USE=-unicode CFLAGS=-O2 emerge less&&quickpkg less&&
mv /usr/port.../less... /tmp/less-unicode.tbz2&&bunzip /tmp/less-unicode.tbz2
2.USE=+unicode CFLAGS=-O2 emerge less&&quickpkg less&&
mv /usr/port.../less... /tmp/less+unicode.tbz2&&bunzip /tmp/less+unicode.tbz2
3.diff -a /tmp/less-unicode.tar /tmp/less+unicode.tar
works for me. A "general" less-package and some patchfiles for adding the use-
flags to the tbz2 file
Sorry, no. We don't have resources to produce such things (diskspace, bandwidth,
CPU time, etc.)