On 21 Feb 2001, at 1:31, [EMAIL PROTECTED] wrote:
> On Tue, Feb 20, 2001 at 05:05:52PM -0600, [EMAIL PROTECTED] scribbled:
> > Having said that, one of the things on my list of "ToDos" is to
> > change apkg to generate *.md5 for every file in the package for
> > checking purposes. This would mean:
>
> Every file? That's a hell of a lot of md5suming. Would not a
> single md5sum of all the files suffice?
It's not that bad. Most packages don't have that many files.
> But, why would you want to md5sum a directory?
I didn't say I wanted to.
> Why not md5sum the concatenation of all files in the dir, or even
> of all the md5sums of all the files in the dir?
That's the idea: generate md5sums for all files in the directory.
However....
> If your challenge is to step through the list, using each line as an
> argument for md5sum, I can help, with a method Charles devised when I
> asked for help doing something similar for mp3s... :)
Actually, I've gotten something working, but I think it's sort of
kludgey. Here is a more concise description of the possible input to
md5sum:
directory
wildcard-directory
file
wildcard-file
...so - which one is it? This has to be massaged for md5sum... also,
a directory needs to be recursed into - I don't think my current
checksumming does this.
Another problem is that the ENTIRE path needs to be generated; this
is also problematic...
Let me think; this is what I need:
directory: find $(fullpath $1) ! -type d
wildcard-directory: find `echo $(fullpath $1)` ! -type d
file: echo $(fullpath $1)
wildcard-file: echo $(fullpath $1)
....hmmm.... or something like that.
> Does your busybox find support -exec?
No.
--
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
[EMAIL PROTECTED]
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
