1 |
Dnia 2013-08-21, o godz. 14:49:45 |
2 |
Pacho Ramos <pacho@g.o> napisał(a): |
3 |
|
4 |
> El mié, 21-08-2013 a las 14:35 +0200, Ulrich Mueller escribió: |
5 |
> > >>>>> On Wed, 21 Aug 2013, Pacho Ramos wrote: |
6 |
> > |
7 |
> > > Could appending to DOCS be allowed? I have seen a lot of time of me |
8 |
> > > needing to install all docs "manually" only to add a doc file over |
9 |
> > > default DOCS. Would be interesting to simply do: DOCS+=( otherfile ) |
10 |
> > |
11 |
> > > instead of needing to specify all files handled by the install |
12 |
> > > function |
13 |
> > |
14 |
> > We discussed this in bug 449806 already. Problems that need to be |
15 |
> > solved: |
16 |
> > - If we want to keep support for both array and whitespace-separated |
17 |
> > list then we can't preset a global variable. |
18 |
> > - How do we distinguish between DOCS being unset (i.e. install default |
19 |
> > docs) and DOCS being empty (i.e. don't install anything)? |
20 |
> > - We could introduce some special syntax like a __default__ marker, |
21 |
> > but do we want such in-band signalling? |
22 |
> |
23 |
> Well, the last comment by mgorny in bug report after some suggestions |
24 |
> rised there made me think I should wait for the einstalldocs "thing" :/ |
25 |
|
26 |
Yes, for something like: |
27 |
|
28 |
src_install() { |
29 |
... |
30 |
einstalldocs |
31 |
dodoc FOO |
32 |
} |
33 |
|
34 |
-- |
35 |
Best regards, |
36 |
Michał Górny |