1 |
> The purpose of this design philosophy is to help ensure a working system without |
2 |
> putting unnecessary restraints on the user. Apologies for not explaining this |
3 |
> earlier; I thought you understood the concept behind the packages file. In any |
4 |
> case, I hope you like the design -- personally, I think it's a good approach. |
5 |
|
6 |
Hmm, ok my idea whould mess up the idea of the packages file. |
7 |
|
8 |
Here is an alternative to the package.mask concept. We can start tagging |
9 |
packages in the cvs tree. |
10 |
So by default you whould checkout the latest rc instead of the in |
11 |
development versions. If you want to |
12 |
add a development version to your system you can checkout manually. |
13 |
Instead of using the gentoo version number for tagging we can use |
14 |
"stable" for all packages not in development. |
15 |
This should be sufficient for the beginning, but in the future I think |
16 |
we need to use the version numbers. |
17 |
The past shows that it is a nice idea to have an allways up to date |
18 |
system, but some updates can create lots of |
19 |
unexpectable bugs. To avoid messing up all our users system, we can |
20 |
instead maintain our different releases |
21 |
separate and make only security fixes to them. So you can allways have a |
22 |
secure rc4,rc5 1.0 1.1 .... |
23 |
|
24 |
achim~ |