| 1 |
Hi! |
| 2 |
|
| 3 |
On 20:42 Mon 19 Sep 2011, Markos Chandras wrote: |
| 4 |
> On 09/19/11 20:30, "Paweł Hajdan, Jr." wrote: |
| 5 |
> > I uploaded my script for finding reverse dependencies here: |
| 6 |
> > http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=summary |
| 7 |
> > |
| 8 |
> > Advantages over existing solutions (browsing to websites like |
| 9 |
> > tinderbox or qa-reports): |
| 10 |
> > |
| 11 |
> > - only prints stable packages when run on a stable system (no need |
| 12 |
> > to manually filter out things) - takes a list of packages as input, |
| 13 |
> > making it more effective for a batch workflow (we're short on time, |
| 14 |
> > batching is often critical) - produces output that can be fed to |
| 15 |
> > emerge after stripping comment lines (no junk after package names); |
| 16 |
> > again this is for the batch workflow |
| 17 |
> > |
| 18 |
> > It is still reasonably fast. On my machine it completes within 30 |
| 19 |
> > seconds. |
| 20 |
> > |
| 21 |
> > Comments welcome. I'd be very happy to adapt this to your needs. My |
| 22 |
> > main goal is to share those little scripts I use with others so we |
| 23 |
> > can all become more productive (and have more time for other |
| 24 |
> > things). |
| 25 |
> > |
| 26 |
> > Paweł |
| 27 |
> > |
| 28 |
> |
| 29 |
> Maybe it is about time to gather all the arch-testing scripts we have |
| 30 |
> around, package them as a single tarball and create an ebuild for that? |
| 31 |
|
| 32 |
For me personally I'm gathering all functionality inside tatt which aims |
| 33 |
at doing it all from one executable. Some x86 arch testers use it |
| 34 |
already, but I must admit that development has been slow. |
| 35 |
|
| 36 |
People (including me) seem to find it hard to start using somebody elses |
| 37 |
tools. There was app-portage/gatt which I tried out when I became an |
| 38 |
arch tester, but I found it insanely complicated, so I wrote tatt. I |
| 39 |
assume that at some point people will find tatt too complicated and |
| 40 |
write yaatt (yet another ... ). In principle, this is what Pawel is |
| 41 |
doing. I think an ecosystem of different arch testing tools is really |
| 42 |
useful. |
| 43 |
|
| 44 |
Let's have a page in our docs where everybody can explain his or her |
| 45 |
tool. Where in the hierarchy should the page be? How about: |
| 46 |
http://www.gentoo.org/proj/en/base/arch-testing |
| 47 |
|
| 48 |
Cheers, |
| 49 |
Thomas |
| 50 |
|
| 51 |
|
| 52 |
-- |
| 53 |
Thomas Kahle |
| 54 |
http://dev.gentoo.org/~tomka/ |
Archives