On 06/26/2011 06:33 AM, William Hubbs wrote:
> That's correct, everything has to be in the repository if you use it.
> The advantage of doing it that way is that anyone can come along
> whenever they want to and generate a tarball that exactly matches the
> one we generate at release time. Doing it the other way, they can't.

Frankly, I don't care about that feature.  I care about content and Git
tags that lead to content.


>> Alright.  On the other hand without dependencies you get nowhere: either
>> you don#t have features or you build every wheel yourself.
>  
>  I'm not quite sure what you mean here.

I was trying to say that you get quite something for the cost you put
into dependencies.  You save re-writing things yourself and you get more
features for free.  That's what the cost is for.


>>    Plus Asciidoc syntax is more readable.
> 
> You can use man ./catalyst.1 to read the man page.

Are you serious?  I want syntax to be readable while editing, not after
pre-processing.  With that argument we could be writing man pages in
assembly.

> 
>>
>>  - Man page keeps itself in sync on
>>
>>    - list of subarches
>>
>>    - version of catalyst
>>
>>  - Option to make XHTML from the same source
>  
>  The cons of the new approach, as I see it, are:
> 
> * auto generated content in tarballs makes it impossible to create the
> exact same tarball twice.

Again, i don't care.


> * Now we need to have a build time dependency, at least for the live
> ebuild, which pulls in about 34mb of downloads just to build the man
> page.
> 
> Since we are just talking about a man page, imho this is a lot of bloat
> for very little gain.

I disagree on bloat and on little gain.

If you insist on changing status quo I would like to call in a vote.

Best,



Sebastian