1 |
On Tue, 2013-02-26 at 20:40 -0500, W. Trevor King wrote: |
2 |
> On Tue, Feb 26, 2013 at 05:30:40PM -0800, Brian Dolbec wrote: |
3 |
> > My aim for now is to debug the hell out of it, to stabilize all the |
4 |
> > existing changes, BEFORE doing a ton more changes. That will also give |
5 |
> > me more experience in how catalyst is used, possibly ideas how to change |
6 |
> > it for the better. I'll fix the doc's generation and make a setup.py |
7 |
> > and new 9999 ebuild. |
8 |
> |
9 |
> I'm not suggesting additional changes on top of yours, I'm suggesting |
10 |
> new ones underneath yours, or alternatives to your current series. It |
11 |
> seems a shame to spend time testing a work in progress, since you'll |
12 |
> probably want to re-test the final form before merging. I'm trying to |
13 |
> help polish your series down before we invest a lot of time testing. |
14 |
> |
15 |
|
16 |
NNNNNNNNNNNNOOOOOOOOOOOOOOOOOOOOOOOO :( not more rebasing I spent |
17 |
several days just tracking down and fixing rebase errors. Fix a few, |
18 |
that in turn caused more errors... |
19 |
|
20 |
You and I both know that the code is likely to be broken at times while |
21 |
doing many of the code changes needed to fix it. The original code was |
22 |
horrible, not all of it, but... The time for polish is later when the |
23 |
majority of the changes are done. I want to move forward, not churn in |
24 |
circles, rebasing, fixing conflicts, forever waiting for a commit to be |
25 |
reviewed & merged. One of the big reasons I started on catalyst was to |
26 |
remove the hardcoded paths everywhere that was preventing the tree |
27 |
migration away from /usr/portage. That has been largely accomplished, |
28 |
although not really tested. |
29 |
|
30 |
The reason I wanted to do more testing, is so far I've only done |
31 |
snapshot, stage1 thru 3. I've done the major restructure of the python |
32 |
layout. I want to get everything working, not 100% bug free, before |
33 |
moving on. That will make it easier to figure out where something got |
34 |
broken while doing the changes. Call it a midterm exam ;) to see where |
35 |
we stand. |
36 |
|
37 |
So I wouldn't mind working in a branch for now, somewhere we can all |
38 |
participate in pushing commits to in order to achieve our end goal. |
39 |
Then later when it's mostly done, we can look to moving it to master. |
40 |
Finish debugging and polishing it. |
41 |
|
42 |
|
43 |
|
44 |
> Cheers, |
45 |
> Trevor |
46 |
> |