On Thu, 18 Sep 2003 18:55:13 +0100, Gordan wrote: > On Thursday 18 September 2003 18:39, Michael Schierl wrote: > >> Try to let FIW build the container for you or use the "insert a file/NIM" >> function for inserting it (into a CHK key, *not* into any other key >> type![1]); insterting it inside a freesite does not work... There are some >> strange assumptions made on the metadata for containers (e.g. there *must* >> be a Info.Format in the manifest on the "final" key, but *may not* be one >> in any intermediate manifests. >> >> If you upload a .zip as part of a freesite, the Info.Format gets into the >> site's mapfile instead of the mapfile of the final key, so containers >> simply used as .zip do not work. > > Is there a sensible/convenient way to insert many zips as containers, while > still keeping them accessible (referenced in the manifest) using a human > readable path under the SSK site key?
if you have already built that containers up, no. (not with FIW.) > SSK@<somepublickey>/SomeSite//a.zip//a0.html > SSK@<somepublickey>/SomeSite//a.zip//a1.html > ... > SSK@<somepublickey>/SomeSite//z.zip//z9.html > > Is there a reasonable way to achieve this? Effectively, treat all zips as > containers by default? by default is evil. there are guys who want to refresh one shot sites... perhaps add a config option for it? I personally do not see a need for it atm (and have some other projects w/ higher priority than FIW atm). mihi _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
