On 18/05/16 07:43, Michał Górny wrote:
> On Wed, 18 May 2016 04:07:07 +0100
> "M. J. Everitt" wrote:
>
>> I've just been party to a discussion over in the Proxy Maintainers
>> channel .. and the subject of correct ways to install documentation
>> popped up. It seems to me
On Wed, 18 May 2016 04:07:07 +0100
"M. J. Everitt" wrote:
> I've just been party to a discussion over in the Proxy Maintainers
> channel .. and the subject of correct ways to install documentation
> popped up. It seems to me rather quirky, that there is no middle ground
> in
> On Wed, 18 May 2016, Kent Fredric wrote:
> On 18 May 2016 at 17:40, Ulrich Mueller wrote:
>> Only two lines. Do you think this is untidy?
> It only becomes untidy where you don't already have a src_install.
> Then it becomes 4 lines.
> 4 lines of which 3 are redundant
On Wed, May 18, 2016 at 05:44:28PM +1200, Kent Fredric wrote:
> On 18 May 2016 at 17:40, Ulrich Mueller wrote:
> > Only two lines. Do you think this is untidy?
>
>
> It only becomes untidy where you don't already have a src_install.
>
> Then it becomes 4 lines.
>
> 4 lines of
On 18 May 2016 at 17:40, Ulrich Mueller wrote:
> Only two lines. Do you think this is untidy?
It only becomes untidy where you don't already have a src_install.
Then it becomes 4 lines.
4 lines of which 3 are redundant and simply re-codify existing behaviour.
--
Kent
> On Wed, 18 May 2016, M J Everitt wrote:
> My idea thus, was inspired by the simple bash DOCS+= ( ) statement,
> that would allow you to append files/folders to the installdocs
> list, assuming that DOCS was pre-populated with an existing set of
> files. Obviously the status quo is set for
I've just been party to a discussion over in the Proxy Maintainers
channel .. and the subject of correct ways to install documentation
popped up. It seems to me rather quirky, that there is no middle ground
in (for example) EAPI6 to have the default documentation installed per