1 |
One item I have not seen is the possibility of auto-rewinding something |
2 |
like the libpng problem back to a working system. CVS is a case in |
3 |
point - when a build is broken, go back a version and build again. |
4 |
Williams checkpoint idea sounds similar to CVS in the way you can |
5 |
specify versions. |
6 |
|
7 |
Now this would be a *real* advance in taking some of the risk out of |
8 |
bleeding edge for all users, average and developer. |
9 |
|
10 |
BillK |
11 |
|
12 |
|
13 |
On Sat, 2002-04-20 at 10:15, William McArthur wrote: |
14 |
> [Sorry if this is a duplicate, I'm currently demonstrating a severe lack |
15 |
> of email skills.] |
16 |
> |
17 |
> The other day there was a discussion on IRC about improving the |
18 |
> stability of the distro as a whole. The popular idea at the time was a |
19 |
> stability metric applied to each package based on a few things. The |
20 |
> following is my thoughts on how to improve the situation with minimal |
21 |
> developer effort. |
22 |
> |
23 |
> First, I don't think the stability metric idea won't have it's desired |
24 |
> effect. The libpng problems would not be prevented with a stability |
25 |
> metric. The problem was not with the package specificlly but the |
26 |
> interaction between pacakges. Specifically packages that linked with |
27 |
> libpng and expected libpng-1.0.* . |