| 1 |
Just two points: |
| 2 |
|
| 3 |
- standards should not be set by the primary package manager |
| 4 |
- the primary package manager does not have to be developed by Gentoo. |
| 5 |
|
| 6 |
More about it below: |
| 7 |
|
| 8 |
maillog: 20/05/2006-14:54:18(+0200): Paul de Vrieze types |
| 9 |
> The primary package manager is the package manager that sets the |
| 10 |
> standards for the tree. All ebuilds in the tree must function |
| 11 |
> with the primary package manager. As the primary package manager |
| 12 |
> sets the standard it does not have to maintain compatibility with |
| 13 |
> other package managers. |
| 14 |
|
| 15 |
I pesonally hate the way this sounds. It implies that the package |
| 16 |
manager comes before the standards while it should be the other way |
| 17 |
around. Plus, it would not solve the main problem -- that there are no |
| 18 |
set standards for the tree. You accept the GLEP like this and there will |
| 19 |
continue to be no standards. |
| 20 |
|
| 21 |
The process should go like this: |
| 22 |
|
| 23 |
1. Standars are set (by the council or whatever). |
| 24 |
2. They are implemented in the official package manager. |
| 25 |
3. Other package managers follow suit. |
| 26 |
|
| 27 |
Take the application servers as a good example. You have Java Servlet |
| 28 |
Technology, and JavaServer Pages Technology. So far, so good. These are |
| 29 |
developed by Sun. And you also have Apache Tomcat which is the official |
| 30 |
reference implementation. So you have the standards set by Sun, and you |
| 31 |
have an open community implementing them in the "official" container |
| 32 |
*later*. And pay attention that these are not maintained by the same |
| 33 |
organization. |
| 34 |
|
| 35 |
And what about the web. You have the W3C that sets the standards for web |
| 36 |
pages. And you have no single browser to implement them all. So, in |
| 37 |
order for a package manager to be recognized by Gentoo it should not |
| 38 |
implement *all* standards. I.e. if you have news delivered with the |
| 39 |
tree, you could support a package manager that cannot read the news as |
| 40 |
primary. After all this is not a major feature and does not contradict |
| 41 |
"All ebuilds should work with the primary package manager". And you can |
| 42 |
have a separate news reader the cooperates with the primary package |
| 43 |
manager or not. |
| 44 |
|
| 45 |
-- |
| 46 |
\ Georgi Georgiev \ Ignorance is when you don't know anything \ |
| 47 |
/ chutz@×××.net / and somebody finds it out. / |
| 48 |
\ http://www.gg3.net/ \ \ |
Archives