goran.hultgren at bluefish.se wrote:
> Julian Fitzell <julian at beta4.com> wrote:
> > Bill Schwab wrote:
> > > Goran,
> > > 
> > > I'm glad to see that you are planning to include a smart cache soon.  If it's easy to do, it would be nice to have contrtol over the path to the cache directory, probably relative to the image directory.  SM already makes a subdirectory, but it still puts files (lots of them) in the image directory, and I would rather be able to prevent that for the benefit of my backup system.
> > > 
> > 
> > I actually fixed this in my image at work last week.
> > 
> > I figured I wouldn't post it because Goran is working busily on the new 
> > SqueakMap but since there may be interest I'll post it anyway.
> 
> :-) No problem. I will integrate those changes and more when I get to
> that part.
> I am thinking of this structure:
> 
> /sm/squeakmap.1.lg (renamed to use .lg instead of .log according to
> suggestion)
> /sm/packagecache/<uuid>/<autoversion>/downloadedfile
> 
> So, each package gets its own directory with the UUID as the name. Since
> packages can be renamed this seemed safest - even if it isn't "user
> friendly" to look at. Any better suggestions?
> 
> Then in the directory we have one directory for each release using the
> automatic version number as name (Stephen Pairs VersionNumber class) -
> typically "1", "2" etc, created when a release is downloaded. And then
> the downloaded file is in there.
> 
> The general download service should of course first check if the file is
> available on disk. A new choice called "forced download" or something
> could be good to have too.
> 
> Does this sound good?

Yes!

--Hannes