Comments on: Figuring out which files are touched while installing software http://blog.johnford.org/figuring-out-which-files-are-touched-while-installing-software/ the things that I remembered to write about Sat, 04 Feb 2012 01:04:01 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Kent http://blog.johnford.org/figuring-out-which-files-are-touched-while-installing-software/comment-page-1/#comment-6264 Kent Sun, 30 Oct 2011 23:42:16 +0000 http://blog.johnford.info/?p=223#comment-6264 Interesting insight on that code snippet, I would also have to agree why not just move the scratchbox into a new filesystem? It just seems more efficient to do it Mooks way. Interesting insight on that code snippet, I would also have to agree why not just move the scratchbox into a new filesystem? It just seems more efficient to do it Mooks way.

]]> By: JimB http://blog.johnford.org/figuring-out-which-files-are-touched-while-installing-software/comment-page-1/#comment-3393 JimB Sat, 06 Mar 2010 08:32:14 +0000 http://blog.johnford.info/?p=223#comment-3393 Nip it in the bud; use -prune. Something like: find -mount -type f -exec openssl md5 '{}' \; -wholename '/builds/scratchbox' -prune Nip it in the bud; use -prune. Something like:

find -mount -type f -exec openssl md5 ‘{}’ \; -wholename ‘/builds/scratchbox’ -prune

]]> By: Mook http://blog.johnford.org/figuring-out-which-files-are-touched-while-installing-software/comment-page-1/#comment-3391 Mook Sat, 06 Mar 2010 07:10:50 +0000 http://blog.johnford.info/?p=223#comment-3391 Wouldn't it have been easier to just move /builds/scratchbox into a different filesystem? (In which case your find command would automatically skip it - and therefore not hash anything there.) Presumably you were going to clobber the existing installs anyway (and therefore needed a tarball of a new root). But then, it probably was all fast enough for you anyway ;) (I wonder whether m.group('file').startswith("/builds/scratchbox/") would be faster or slower? On the one hand, it's not re; on the other, it doesn't get a precompilation advantage...) Wouldn’t it have been easier to just move /builds/scratchbox into a different filesystem? (In which case your find command would automatically skip it – and therefore not hash anything there.) Presumably you were going to clobber the existing installs anyway (and therefore needed a tarball of a new root).

But then, it probably was all fast enough for you anyway ;)

(I wonder whether m.group(‘file’).startswith(“/builds/scratchbox/”) would be faster or slower? On the one hand, it’s not re; on the other, it doesn’t get a precompilation advantage…)

]]> By: Tony Mechelynck http://blog.johnford.org/figuring-out-which-files-are-touched-while-installing-software/comment-page-1/#comment-3384 Tony Mechelynck Fri, 05 Mar 2010 21:47:48 +0000 http://blog.johnford.info/?p=223#comment-3384 Why not just diff -U 0 file-list1 file-list2 | grep -vF /builds/scratchbox/ (or similar) to display just those differences that don't contain the string /builds/scratchbox/ ? Why not just

diff -U 0 file-list1 file-list2 | grep -vF /builds/scratchbox/

(or similar) to display just those differences that don’t contain the string /builds/scratchbox/ ?

]]>