| 1 |
perhaps i wasn't clear enough. say ebuild foo has KEYWORDS="x86", and |
| 2 |
all it's dependencies have KEYWORDS="x86 ppc". barring any x86-centric |
| 3 |
stuff in the build, there's a fine chance it's going to build and run on |
| 4 |
ppc. my script finds these types of cases and tries to build them, |
| 5 |
logging whether each was built or not. this is useful for a ppc dev for |
| 6 |
keywording purposes. (feel free to substitute sparc or alpha (or the |
| 7 |
rare x86) for ppc above). |
| 8 |
|
| 9 |
note: no one gets unwanted mails with this. |
| 10 |
|
| 11 |
nall. |
| 12 |
|
| 13 |
|
| 14 |
On Wed, 2002-12-11 at 12:11, Brian Magnuson wrote: |
| 15 |
> * Jon Nall <nall@g.o> [2002-12-11 12:45]: |
| 16 |
> |
| 17 |
> > in truth, my autobuilder is going to be used to automate building of |
| 18 |
> > packages that aren't already keyworded for a give ARCH. it just happens |
| 19 |
> > that it can be used for what riyad suggests too. |
| 20 |
> > |
| 21 |
> |
| 22 |
> So you intend this script to be used for builds that have been commited but |
| 23 |
> are still under active development and havn't been declared safe for anyone? |
| 24 |
> That sounds like a useful tool, but something that would be run individually |
| 25 |
> by the developer of the ebuild instead of continually looping through all such |
| 26 |
> builds. Since the ebuilds themselves are expected to be unstable they will |
| 27 |
> likely generate lots of build failures and unless your reporting mechanism is |
| 28 |
> totally passive I think people might get kinda tired of hearing from your |
| 29 |
> script. :) |
| 30 |
> |
| 31 |
> -- |
| 32 |
> gentoo-dev@g.o mailing list |
| 33 |
> |
Archives