1 |
> > > If that 900 line diff is 'drop kdebuild', I suggest you don't |
2 |
> > > bother. |
3 |
> > |
4 |
> > Actually, I think that this would be a good idea. kdebuild was never |
5 |
> > used in the main tree |
6 |
> |
7 |
> But it was an official Gentoo project, and it was used in a repository |
8 |
> run by the Gentoo KDE team. |
9 |
So the Gentoo KDE team could decide to keep the documentation. As |
10 |
representative of the KDE team I say that we have no interest in keeping this |
11 |
historical error around any more. Especially as it never worked (well, not |
12 |
with portage at least), so none of our users would be affected. |
13 |
|
14 |
Also, it was only official in the sense that the KDE team decided to start it, |
15 |
then abandon it and leave Gentoo. In the same sense package.mask as a |
16 |
directory is officially supported (used by the KDE team, temporarily removed |
17 |
for legacy package managers). |
18 |
|
19 |
> Remember that EAPI support is needed to be |
20 |
> able to uninstall a package that was installed with a particular EAPI, |
21 |
> so EAPIs can't be removed even when they're no longer in use. |
22 |
Yeah, like, uhm, yeah, no. See above. |
23 |
> |
24 |
> > and the conditionals needed for it only add |
25 |
> > clutter that makes reading and editing the source more difficult. |
26 |
> |
27 |
> Ok, so we remove the conditionals and just keep it in unconditionally. |
28 |
That would imply having it in the official version, which explicitly goes |
29 |
against a prior council decision. |
30 |
|
31 |
Remember the bash 3.0/3.2 change yesterday? Where you said you don't have the |
32 |
power to change it? Yeah, neither do you have it here ... adding kdebuild-1 |
33 |
unconditionally is not an option. |
34 |
|
35 |
> Keeping it documented hurts no-one. |
36 |
I disagree. It makes accidental errors more likely (like having kdebuild |
37 |
enabled in a version that looks authorative) and makes editing a pain because |
38 |
most tables are redundant (in the sense that they aren't needed and in the |
39 |
sense that they are there twice to accomodate the kdebuild phantom) |
40 |
|
41 |
It also doesn't document anything that is related to the main gentoo tree, so |
42 |
it makes no sense to keep it in the document that is supposed to document |
43 |
_that_. |
44 |
|
45 |
> It also reduces the amount of work |
46 |
> we have to do as features that it has slowly end up in |
47 |
> Portage-supported EAPIs -- EAPI 3 would have taken much longer had we |
48 |
> had to rewrite it all from scratch. |
49 |
That assumes that there's any overlap between future EAPIs and kdebuild, which |
50 |
is quite optimistic. |
51 |
|
52 |
So I say tag it and remove it, if anyone should be interested in archaeology |
53 |
(s)he can find the right point in the git repo easily and create a |
54 |
historically accurate representation of the Tyrannosaurus Rex. Err, |
55 |
kdebuild-1. |
56 |
|
57 |
|
58 |
Have a nice day, |
59 |
|
60 |
Patrick |