Brock Pytlik wrote:
> Shawn Walker wrote:
>> There is a major flaw here that just came to mind; notably, that the 
>> catalog, index, and updatelog directory all have to be included as 
>> part of this.  In other words, if I'm serving a particular version of 
>> a catalog, then I also have to serve a corresponding version of the 
>> search index and updatelog.
>>   
> Because the search index is already being built in an alternate location 
> then moved into place when it's able to, it would be a fairly simple 
> change to alter this behavior to not replace the current search index 
> until actually told to.

Since I need the ability to serve any previous snapshot, I'd also need 
to snapshot the search data, etc.  One copy of the search data alone 
wouldn't suffice, unless I'm misunderstanding you.

At the moment, I'm thinking the filesystem layout needs to change for 
the depot from:

repo_dir/
   catalog/
   file/
   index/
   pkg/
   trans/
   updatelog/
   cfg_cache

to:

repo_dir/
   file/
   metasets/
     {metaset_name}/
       catalog/
       index/
       updatelog/
   pkg/
   trans/
   cfg_cache

The above structure would provide the ability to serve a specific 
snapshot of the catalog/updatelog/search for the repository.  Note I 
purposefully left the pkg/ directory at the top level, since regardless 
of which metaset was being served, the older manifests should still be 
present.

I'm inclined to rename pkg/ to manifest/ as well...

Thoughts?

-- 
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to