| 1 |
No system is perfect. And such a "permanent" tainting could be mentiond |
| 2 |
in the warning or manual. |
| 3 |
But this system would still be helpfull and reduce the nuber of bogous |
| 4 |
bugreports. |
| 5 |
A package can be tainted when a RDEPEND package is upgraded (if known to |
| 6 |
break things), like the current python upgrade. |
| 7 |
|
| 8 |
Taint might be a bad word, but a state flag describing the official |
| 9 |
stableness of installed packages. |
| 10 |
|
| 11 |
-John |
| 12 |
|
| 13 |
On Fri, 2004-01-23 at 11:00, Paul de Vrieze wrote: |
| 14 |
> On Friday 23 January 2004 08:05, John Nilsson wrote: |
| 15 |
> > Ok, this thread may be a waste of time but still... |
| 16 |
> > |
| 17 |
> > Portage could "taint" packages that is installed with unsupported or |
| 18 |
> > tainted packages as dependencies. Have portage give a warning about |
| 19 |
> > tainted packages. |
| 20 |
> |
| 21 |
> The only way this would work would be if the actual merging of a tainted |
| 22 |
> package would taint your whole system forever. Packages can leave their |
| 23 |
> trails for long, very long times and have effects all over the place. So in |
| 24 |
> the end I don't think it works |
| 25 |
> |
| 26 |
> Paul |
Archives