P.S. The whole build system is a compiled artefact. The source code needed to regenerate it is there, but we ship the generated files too. Once I land this docs stuff, the difference between the ./bootstrap and ./configure scripts will become even more apparent. We'll be shipping HTML and a PDF generated from .rst files in our source releases, meaning you don't need TeX (Knuth's best troll ever) installed to build CouchDB.
On 3 November 2012 16:44, Octavian Damiean <[email protected]> wrote: > Compiled artifact in this case means, compiled LESS files to CSS (minified > or not), JavaScript (minified or not) and HTML. So no bytecode, it would > still be readable (except minified JS and CSS are a bit hard to read bit > still plaintext). > > Cheers, > Octavian > > On Sat, Nov 3, 2012 at 5:37 PM, Noah Slater <[email protected]> wrote: > > > > Also, Bob sed: > > > > If the choice is node as a build dependency versus checking in compiled > > > artifacts, I choose node. > > > > > > Perhaps someone can clarify for me what a compiled artefact is? We can't > > ship compiled code. We can ship compressed or package code. But if we're > > compiling code into bytecode or machine code, that is a complete no-no in > > both our repos and our releases. > > > > -- > > NS > > > -- NS
