tag:blogger.com,1999:blog-3888382143307542639.post6666814769092103806..comments2024-11-04T04:11:37.679+00:00Mark Seabornhttp://www.blogger.com/profile/08046205947658697263noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3888382143307542639.post-57569505678703571352008-11-06T10:25:00.000+00:002008-11-06T10:25:00.000+00:00I know about Klik. It did influence my idea of rewriting filenames, although I forgot to mention it in the blog post. Rewriting "/usr" to ".///" has never struck me as a very good idea though, firstly because the chance of collisions, and secondly because it requires changing the current directory, which makes it unsuitable for running any program that takes relative filenames. It may work 90% of the time, but the other 10% of the time you could be totally screwed. Whereas, if you do rewriting on long, randomly-generated filenames instead you can reduce the chance of accidental collision to nil.<BR/><BR/>Klik is basically trying to avoid rebuilding things from source. To a lesser extent Zero-Install is too. I'm not interested in that approach at all. I don't see much potential for these deployment systems if they are dependent on getting binary debs or RPMs from some other project. Like Mark Shuttleworth says, free software is a <A HREF="https://wiki.edubuntu.org/MarkShuttleworth#What%20about%20binary%20compatibility%20between%20distributions?" REL="nofollow">collaborative process based on <I>source code</I></A>.Mark Seabornhttps://www.blogger.com/profile/08046205947658697263noreply@blogger.comtag:blogger.com,1999:blog-3888382143307542639.post-57820330910070379832008-11-06T01:51:00.000+00:002008-11-06T01:51:00.000+00:00That is roughly what klik (klik.atekon.de) does, but it does it even a bit more cleverly... patching absolute paths into relative paths (/usr -&gt; .///) and using a wrapper script. Works 90% of the time. klik2 will use a real per-process overlay filesystem though, which is even cooler...Anonymousnoreply@blogger.com