| 1 |
Mark Guertin wrote: |
| 2 |
|
| 3 |
> The whole objective with this is to actually provide the users with a |
| 4 |
> 'stable' working setup, but also be quick abot it (unlike debian's |
| 5 |
> completely seperate trees). Thing's generally won't live as ~arch for |
| 6 |
> long at all, just for initial testing phase. |
| 7 |
|
| 8 |
This is great news because it happened a couple times that i emerged a |
| 9 |
new ebuild that wasn't simply working (tightVNC and Postfix comes to |
| 10 |
mind) so i had to revert to the previous version manually. Previously i |
| 11 |
would never schedule an "emerge rsync && emerge world -u" because it |
| 12 |
would often break existing packages and left my system not working properly. |
| 13 |
|
| 14 |
This new feature is really great, however it would be great to be able |
| 15 |
to specify for which packages you want to enable this. You could be |
| 16 |
using stable packages everywhere except for certain softwares which you |
| 17 |
want the latest version and don't care for stability (web browsers or |
| 18 |
games for example). |
| 19 |
|
| 20 |
|
| 21 |
-- |
| 22 |
Louis-Philippe Brochu |
Archives