Jeremy Huntwork wrote: > Hello, > > So I finally got a free evening and the energy to sit down and get > conceptual. This is the result: > http://linuxfromscratch.org/~jhuntwork/php-test/ > > Before replying about all that you see is wrong with it ;) keep the > following in mind: > > This is a rough draft! A proof-of-concept only, designed to show > possibilities and open up discussion/ideas. Think stick-figure.
Glibc is not the best example for discussion. I requested such sample page for bash, not for glibc, for a reason: bash needs a specific patch in the RPM case, and I don't see the way to force such PM-specific instructions in the current framework. Although even for glibc, there is something to discuss: * making one big RPM package with both the shared library and its headers is technically incorrect (this is not so severe for glibc, but think about gradual updates from libssl.so.0.9.8 to libssl.so.0.9.9, and that's impossible without removing a lot of dependent packages if one doesn't package the conflicting headers in a separate RPM file); * the current framework doesn't allow for such split; * editors that don't use a package manager have to be taught about this. As for the generated pages: if the LiveCD is to be revived, this means packaging PHP and some lightweight HTTP server on it (I prefer lighttpd). It also means increased requirements for mirrors, both in terms of available software and the level of trust to the book authors (i.e., so that they don't put a malicious PHP script in order to compromise a lot of mirrors at once, or just unintentionally introduce a security hole). Are we ready to this? P.S. Sorry for several hackish HTTP requests to www.linuxfromscratch.org. So far, I have found no obvious way to compromise the scripts in the current PHP configuration. -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
