Last modified 6 April 1999

============================================================================================================
============================================================================================================

			The PEAKster's GUIDE To Naming MacOS-X Submissions

TOP LEVEL: 	http://www.peak.org/apple/macosx/server/
aka		 ftp://ftp.peak.org/pub/apple/macosx/server/

SUBMISSIONS:	ftp://ftp.peak.org/pub/apple/submissions
		(NOTE: this current is not working
			Please use /pub/openstep/submissions for the time)

EMAIL:		[email protected]

NOTE: 		Please email us to tell us when you upload something!
				



The best way to see how files are named is by looking at good examples.

There are some bad examples (we're working to correct that!) so here's a good example to use as a guide:

	Samba-2.0.3-P-b.tgz

This tells me everything I need to know.

	"Samba"		gives me the _NAME_ field

	"2.0.3" 	tells me the _VERSION NUMBER_

	"P" 		tells me that it is PowerPC _ARCHITECTURE_ (or HARDWARE)
	
	"b"		tells me that is is the DISTRIBUTION is "BINARY" only
	
	"tgz"		tells me the ARCHIVE TYPE is "tar" and "gzip"


"NAME" is obviously up to you, but should not include any version information.

"VERSION NUMBER" depends on the release number.  If the above example was
	as BETA or ALPHA release, the version number would have
	shown that like this:
	
		2.0.3b	for beta
		2.0.3a	for alpha
	
	Now assume someone ports Samba 2.0.3 to MacOSX, and then finds there
	are some bugs that they fix.  However, the Samba release is still at
	2.0.3.  In that case, use an "_" followed by the special patch number:
	
	"2.0.3_1" would mean "Version 2.0.3 with ONE special revision set
		specifically to MacOSX Server.

"ARCHITECTURE" must be one or more of the following:
	"P" for PowerPC
	"I" for Intel (hey, we can hope, can't we?)
	"Y" for Yellow Box
	
	If more than one ARCHITECTURE is included, use all applicable letters
	in the order given above (ie Intel and PPC would be "PI" not "IP")
	This is important for automatic parsing of information.

"DISTRIBUTION" must be one or more of the following:
	"s" for Source Code (*)
	"b" for Binary
	"d" for documentation or other configuration materials
	
	If more than one are included, use all applicable letters in the order
	given above (ie if both binary are source are included, use "sb" not "bs"
	and if all three are included, use "sbd").  
	This is important for automatic parsing of information.

"ARCHIVE TYPE" must be one of the following
	.tgz	for files that have been archived using tar and gzip 
		Note: .tar.gz should no longer be used.  Filenames are long enough :-)

	.gnutar.gz	for files that have been archived using gnutar and gzip

	.zip	for Windows files which have been archived using ZIP
	
	.exe	for Windows self-extracting files


============================================================================================================
README files

Each submission should have an ASCII readme (feel free to include an HTML or RTF version also, but please make sure you have at least a brief summary in ASCII)

REQUIRED FIELDS
	NAME
	VERSION NUMBER

OPTIONAL FIELDS

	The following fields should only be used if there are more than one README files

	ARCHITECTURE (If needed, for example one PPC and one for INTEL)
	DISTRIBUTION (If needed, for example one for Source code and one for Binary)
	ARCHIVE TYPE (If needed, for example one .tgz and one .zip)

Example:

	The README file for "Samba-2.0.3-P-b.tgz" should be:
	
		Samba-2.0.3.README
		
	Unless there was also an Intel version (Samba-2.0.3-I-b.tgz) in which case the README
	files would be
	
		Samba-2.0.3-P.README
		Samba-2.0.3-I.README
	
	Or if there was also a Source distribution (that had a separate README), in which case
	they would be named
	
		Samba-2.0.3-b.README
		Samba-2.0.3-s.README

============================================================================================================

FIELD SEPARTOR

Note that all fields are separated by a "-" rather than a "." with the following exceptions:

	VERSION NUMBERs should have "." to indicate release number, but before
		and after the numbers should be "-"

	For example:
		Samba-2.0.3-P-b.tgz	NOT Samba-2-0-3-P-b.tgz



		
	README and ARCHIVE TYPE suffixes should follow a "."

	For example:
		Samba-2.0.3.README >> YES		Samba-2.0.3-P-b.tgz >> YES

		Samba-2.0.3-README >> NO		Samba-2.0.3-P-b-tgz >> NO

	
============================================================================================================
	
	IF YOU ARE TRIED TO UPLOAD A NEW FILE AND IT DID NOT WORK:

	Please email <[email protected]> and let us know:
		 
		- the name of the file you tried to upload
		
		- how you tried to upload it
		
		- what (if any) error messages you were given
		
		- where we can download a copy of this file
			ex: If you have it on your web page, 
			let us know where the webpage is

IF YOU NEED HELP USING THIS SITE

	Please email your question to <[email protected]> and
	we will try to answer your question

      Name                            Last modified       Size  Description


[DIR] Parent Directory                05-Sep-2005 20:58      -  
[CMP] dumpkeymap-4-PI-sbd.tgz         05-Sep-2005 20:49    50k  
[TXT] dumpkeymap-4-PI-sbd.README      05-Sep-2005 20:49     4k  
[CMP] StoneSuperSeven-Server-1.tar.gz 05-Sep-2005 20:50   9.8M  
[TXT] StoneSuperSeven-OSX.README      05-Sep-2005 20:50     4k  
[CMP] StoneSuperSeven-OSX-1.tar.gz    05-Sep-2005 20:50   9.4M  
[CMP] RBrowser.2.784.P.b.tar.gz       05-Sep-2005 20:49   971k  
[   ] Mesa3R.dmg                      05-Sep-2005 20:49   4.9M  
[   ] Mesa3.dmg                       05-Sep-2005 20:49   3.3M  
[   ] Mesa.dmg                        05-Sep-2005 20:49   3.5M  
[TXT] Mesa.README                     05-Sep-2005 20:49     1k  


Last modified 6 April 1999

============================================================================================================
============================================================================================================

			The PEAKster's GUIDE To Naming MacOS-X Submissions

TOP LEVEL: 	http://www.peak.org/apple/macosx/server/
aka		 ftp://ftp.peak.org/pub/apple/macosx/server/

SUBMISSIONS:	ftp://ftp.peak.org/pub/apple/submissions
		(NOTE: this current is not working
			Please use /pub/openstep/submissions for the time)

EMAIL:		[email protected]

NOTE: 		Please email us to tell us when you upload something!
				



The best way to see how files are named is by looking at good examples.

There are some bad examples (we're working to correct that!) so here's a good example to use as a guide:

	Samba-2.0.3-P-b.tgz

This tells me everything I need to know.

	"Samba"		gives me the _NAME_ field

	"2.0.3" 	tells me the _VERSION NUMBER_

	"P" 		tells me that it is PowerPC _ARCHITECTURE_ (or HARDWARE)
	
	"b"		tells me that is is the DISTRIBUTION is "BINARY" only
	
	"tgz"		tells me the ARCHIVE TYPE is "tar" and "gzip"


"NAME" is obviously up to you, but should not include any version information.

"VERSION NUMBER" depends on the release number.  If the above example was
	as BETA or ALPHA release, the version number would have
	shown that like this:
	
		2.0.3b	for beta
		2.0.3a	for alpha
	
	Now assume someone ports Samba 2.0.3 to MacOSX, and then finds there
	are some bugs that they fix.  However, the Samba release is still at
	2.0.3.  In that case, use an "_" followed by the special patch number:
	
	"2.0.3_1" would mean "Version 2.0.3 with ONE special revision set
		specifically to MacOSX Server.

"ARCHITECTURE" must be one or more of the following:
	"P" for PowerPC
	"I" for Intel (hey, we can hope, can't we?)
	"Y" for Yellow Box
	
	If more than one ARCHITECTURE is included, use all applicable letters
	in the order given above (ie Intel and PPC would be "PI" not "IP")
	This is important for automatic parsing of information.

"DISTRIBUTION" must be one or more of the following:
	"s" for Source Code (*)
	"b" for Binary
	"d" for documentation or other configuration materials
	
	If more than one are included, use all applicable letters in the order
	given above (ie if both binary are source are included, use "sb" not "bs"
	and if all three are included, use "sbd").  
	This is important for automatic parsing of information.

"ARCHIVE TYPE" must be one of the following
	.tgz	for files that have been archived using tar and gzip 
		Note: .tar.gz should no longer be used.  Filenames are long enough :-)

	.gnutar.gz	for files that have been archived using gnutar and gzip

	.zip	for Windows files which have been archived using ZIP
	
	.exe	for Windows self-extracting files


============================================================================================================
README files

Each submission should have an ASCII readme (feel free to include an HTML or RTF version also, but please make sure you have at least a brief summary in ASCII)

REQUIRED FIELDS
	NAME
	VERSION NUMBER

OPTIONAL FIELDS

	The following fields should only be used if there are more than one README files

	ARCHITECTURE (If needed, for example one PPC and one for INTEL)
	DISTRIBUTION (If needed, for example one for Source code and one for Binary)
	ARCHIVE TYPE (If needed, for example one .tgz and one .zip)

Example:

	The README file for "Samba-2.0.3-P-b.tgz" should be:
	
		Samba-2.0.3.README
		
	Unless there was also an Intel version (Samba-2.0.3-I-b.tgz) in which case the README
	files would be
	
		Samba-2.0.3-P.README
		Samba-2.0.3-I.README
	
	Or if there was also a Source distribution (that had a separate README), in which case
	they would be named
	
		Samba-2.0.3-b.README
		Samba-2.0.3-s.README

============================================================================================================

FIELD SEPARTOR

Note that all fields are separated by a "-" rather than a "." with the following exceptions:

	VERSION NUMBERs should have "." to indicate release number, but before
		and after the numbers should be "-"

	For example:
		Samba-2.0.3-P-b.tgz	NOT Samba-2-0-3-P-b.tgz



		
	README and ARCHIVE TYPE suffixes should follow a "."

	For example:
		Samba-2.0.3.README >> YES		Samba-2.0.3-P-b.tgz >> YES

		Samba-2.0.3-README >> NO		Samba-2.0.3-P-b-tgz >> NO

	
============================================================================================================
	
	IF YOU ARE TRIED TO UPLOAD A NEW FILE AND IT DID NOT WORK:

	Please email <[email protected]> and let us know:
		 
		- the name of the file you tried to upload
		
		- how you tried to upload it
		
		- what (if any) error messages you were given
		
		- where we can download a copy of this file
			ex: If you have it on your web page, 
			let us know where the webpage is

IF YOU NEED HELP USING THIS SITE

	Please email your question to <[email protected]> and
	we will try to answer your question