|
|
a
collaboration of the center
for the public domain and unc-ch |
How To Name Things
ibiblio is a participant in the Linux Software Map. To allow indexing and accessibility, it is necessary to follow a few guideline in naming conventions: LSM needs these name parts in this order:
Example: foobar-1.2.3.tar.gz
Please don't use:
Other information in the name: If you have to differentiate between source and binary archives, or between different kinds of binary, or express some kind of build option in the file name, please treat that as a file extension. It should go after the version number. Example
Please *don't* do this: Naming ISO files for DistributionsNaming and uploading iso files for Linux distributions is done in much the same manner as the naming and uploading regular software. The linux distributions aren't handled automatically by the keeper software we use to organize the linux archive, so the strictures on their naming are not as severe as those placed on software. However, there are some generally agreed-upon standards that are currently in use. ISO stands for International Organization for Standardization and is also the ancient Greek word for "equal." There are many ISO standards. In this case we're talking about the ISO 9660 format used by almost all CD-ROMs of Windows, Mac, Unix, and so on. It is sometimes called the High Sierra format. ISO files are generally named using the following convention. The package name is usually 'progname-version-release,' where 'version' is the program version (you should be able to download the program source with this version number from the project's website) and 'release' is the number of the compilation/packaging/patch (from distribution vendor) for that version. An example is: distro-arch-n.jigdo distro-arch-n.template where distro is the name of the distro (like "sarge"), arch is the architecture (like "i386") and n is the disk number (like "1").
send comments to ibiblio linux archive maintainers
|
|
|
||||||