🚀 go-pugleaf

In article <4305@bsu-cs.UUCP> jbwaters@bsu-cs.UUCP (J. Brian Waters) writes:
>In article <8810121728.AA14821@cory.Berkeley.EDU>, dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>>
>>  I say, preserve them all!  Real simple... It's just a longword.
>
>The problem is the zoo file format does not at present reserve 32 bits for file
>attributes.  Given the current format I can preserve 22 bits which should last
>for at least a few more systems software upgrades.

I don't know anything about the zoo format, but if there are any spare (reserved)
longwords laying around, you can do what I did when I ported bru:

    On archive creation:

	Translate the existing defined amiga specific attribute bits to the
	portable attribute bits, and save these as the portable attributes.

	Save a "true copy" of the amiga specific attribute bits in one of
	the formerly "reserved for future use" longwords.

	Set the appropriate bit that specifies that this archive was
	created on an Amiga so the "true copy" is valid.

    On extraction:

	Check the bit that specifies that this archive was created on an
	Amiga.  If it was, restore the attributes from the "true copy"
	of the attributes, stored in the formerly reserved longword.

	If the archive was created on a non-Amiga machine, restore the
	attributes from the portable attributes, translating as necessary.
	Note some attributes may be lost, but that is life.

	Apply any user specified translations to the attributes of the
	file, such as explicitly setting or resetting the "file-archived"
	bit.

If the zoo format definition doesn't have any "reserved for future use"
fields, then I guess you are out of luck...

-Fred
-- 
# Fred Fish, 1346 West 10th Place, Tempe, AZ 85281,  USA
# noao!nud!fishpond!fnf                   (602) 921-1113