1 |
On Wed, 2004-01-21 at 03:32, Pieter Van den Abeele wrote: |
2 |
> another package is also masked and have to restart all over again. The |
3 |
> ppc scripts used to touch files when certain milestones are reached, on |
4 |
> relaunch of the program the fine-grained stages (!= current catalyst |
5 |
> stages) corresponding to the touched files are skipped. |
6 |
|
7 |
I'll work on this. I've been wanting to create a generic tool (a script, |
8 |
at least at first) that can be used to record and check milestones, just |
9 |
to make the implementation cleaner. The implementation of this script is |
10 |
pretty trivial but it'd be nice to have a tool to keep things |
11 |
better-organized, so that ".completed" files aren't being created all |
12 |
over the place with no real organization. |
13 |
|
14 |
something like: |
15 |
|
16 |
./milestone path/to/milestone/dir prep1 |
17 |
result: if prep1 has not been reached, return 1, otherwise 0 |
18 |
|
19 |
|
20 |
./milestone -s path/to/milestone/dir prep1 |
21 |
result: record that milestone "prep1" has been reached |
22 |
|
23 |
|
24 |
./milestone -C path/to/milestone/dir |
25 |
result: reset milestone records |
26 |
|
27 |
It's such a useful thing, that it'd be helpful to have a tiny little |
28 |
tool to handle it, and potentially provide additional interesting |
29 |
capabilties in the future. |
30 |
|
31 |
This tool could be used by portage and catalyst. |
32 |
|
33 |
Regards, |
34 |
|
35 |
Daniel |
36 |
|
37 |
|
38 |
-- |
39 |
gentoo-releng@g.o mailing list |