1 |
* Petteri Räty <betelgeuse@g.o>: |
2 |
> Torsten Veller wrote: |
3 |
> > * Thomas Anderson <gentoofan23@g.o>: |
4 |
> >> Technical Issues: |
5 |
> >> - Prepalldocs |
6 |
> >> Should the 'prepalldocs' be allowed in current EAPIs? |
7 |
> >> |
8 |
> >> Conclusion: |
9 |
> >> Prepalldocs is banned in current EAPIs(0,1,2). It should be |
10 |
> >> removed from ebuilds. Petteri Räty(Betelgeuse) will make QA |
11 |
> >> checks for repoman. |
12 |
> > |
13 |
> > You only did half of your job. |
14 |
> > |
15 |
> > Do we want some docs being compressed, others not? |
16 |
> > Do we want to have compressed docs at all? |
17 |
> > What do you expect from maintainers now? |
18 |
> > |
19 |
> > To me it means: Instead of using prepalldocs I will move the docdir to |
20 |
> > a temporary place and dodoc every file back to docdir. Insane. |
21 |
> > Maybe I add a function named prepalldocs to the ebuilds that does the job. |
22 |
> > |
23 |
> > Thanks. |
24 |
> |
25 |
> Please read the logs. |
26 |
|
27 |
| 15:35 < dev-zero> prepalldocs should be kept internal and usage should be avoided |
28 |
| 15:36 < dev-zero> reason: internal function and change of it's implementation prooves it |
29 |
| 15:36 < dev-zero> if someone want's it's functionality he should propose a solution for a future eapi |
30 |
|
31 |
It is not an internal function. And it's a strange way to prove anything. |
32 |
Around 250 ebuilds use it. So there is probably someone who actually uses this functionality. |
33 |
|
34 |
> prepalldocs has no clearly defined behavior so it should not be used |
35 |
> by ebuilds. |
36 |
|
37 |
It was possible to rectify it. You chose to remove the function completely. |
38 |
|
39 |
> Maintainers should use the public APIs available to them. |
40 |
|
41 |
It's in ebuild.5 for years. |
42 |
And as recruiting lead you probably know that the Developer Handbook contains it as well |
43 |
<http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1>. |
44 |
|
45 |
> If they have a justified need beyond those, they should open a request |
46 |
> for adding needed things to the next EAPI. |
47 |
|
48 |
I will probably do it after i got answers to the questions above. |
49 |
|
50 |
Thanks. |