1 |
On Mon, 19 Dec 2011 01:41:00 -0500 |
2 |
Alexandre Rostovtsev <tetromino@g.o> wrote: |
3 |
|
4 |
> Using /usr/share/doc/$PN-$SLOT with exceptions for packages that have |
5 |
> the same ($PN, $SLOT) but different categories would not scale: it |
6 |
> turns out there are >100 of them in the main tree. |
7 |
|
8 |
And I hope there will be more. We should seriously start splitting |
9 |
packages rather than using old Gentoo bloat like IUSE='perl python |
10 |
foobar foobaz'. |
11 |
|
12 |
> Fortunately, there *is* a neat solution. |
13 |
> |
14 |
> Symlinks. |
15 |
|
16 |
Symlinks are never neat. In this particular case, they just mean |
17 |
someone has failed horribly and now is hoping to fix it taking |
18 |
the path of least resistance. |
19 |
|
20 |
> > 3. CATEGORY and SLOT are Gentoo specific, related to the way how we |
21 |
> > organise our packages. Neither of them should appear in the |
22 |
> > directory structure of installed packages. |
23 |
> |
24 |
> You are correct that categories are Gentoo-specific and are therefore |
25 |
> not ideal for installed paths. However, for generating a stable path |
26 |
> to documentation files, one that does not shift on version bumps and |
27 |
> revbumps, there doesn't seem to be any alternative. |
28 |
|
29 |
To be honest, the whole ${PF} is Gentoo-specific. Package names not |
30 |
necessarily follow upstream ones; sometimes we need to change versions |
31 |
as well to match ${PV} semantics or logic. Perl modules are quite |
32 |
a large case here. |
33 |
|
34 |
Sometimes packages in different categories collide. Right now, devs |
35 |
have to be aware not to install colliding docs -- usually through |
36 |
renaming files. Using category will at least partially fix this. |
37 |
|
38 |
Shifting is unavoidable. SLOTs can change, categories can change, |
39 |
package names can change. Of course, all the mentioned cases are much |
40 |
rarer than PF changing but -- as pointed out before -- these could |
41 |
change without reinstalling packages. |
42 |
|
43 |
If we decided to use such names, the most correct approach would be to |
44 |
have PM handle docmoves as well. But -- on the other hand -- there will |
45 |
be always some hardwired paths which will be updated only on real |
46 |
package rebuild... |
47 |
|
48 |
-- |
49 |
Best regards, |
50 |
Michał Górny |