www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1999/05/17/13:57:18

Sender: richdawe AT bigfoot DOT com
Message-ID: <3740157D.CA756013@bigfoot.com>
Date: Mon, 17 May 1999 14:11:25 +0100
From: Richard Dawe <richdawe AT bigfoot DOT com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.2.1 i586)
MIME-Version: 1.0
To: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: DSM spec 0.2, zippo home page
Reply-To: djgpp-workers AT delorie DOT com

This is a multi-part message in MIME format.
--------------BA27717AF8B9EF54DE67E855
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello.

There's now a home page for zippo/DSM:

http://www.phekda.freeserve.co.uk/richdawe/zippo/

I think DSM shall stand for DJGPP Software Manifest, since it's more than
just a script. Version 0.2 of the DSM spec can be viewed from the web
page, but I have also attached it. I also wrote a few example DSMs that
are fairly simple, just as an example. I'll write a more complicated one
sometime.

I decided that the 'source' and 'documentation' lines should refer to DSM
names rather than package names. Otherwise, zippo would have to search all
DSM files for a package name. If the package name could not be found,
where would zippo search? With the DSM name specified, it could go to
Simtelnet or another DSM archive and download the appropriate DSM, or tell
the user which file to get. These directives are now 'sources-dsm' and
'documentation-dsm'. There is also a 'binaries-dsm' field for
source/documentation packages.

As an aside, I'm writing zippo to work with DJGPP and Linux. This is
principally because I am coding under Linux. I hope to package up my
prototype zippo program, which only uses .mft files, and put onto the home
page sometime.

Bye, Rich =]
--------------BA27717AF8B9EF54DE67E855
Content-Type: text/plain; charset=us-ascii; name="dsm.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="dsm.txt"

DJGPP Software Manifest Specification 0.2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Author:       Richard Dawe <richdawe AT bigfoot DOT com>
Last updated: 1999-05-17

Descriptive Fields
------------------

- In the 'source' and 'documentation' fields below, it is implicit that the
  version for those packages will be the same as for this package, i.e.
  specified by 'version'.

dsm-version: [Version number]
dsm-name: [DSM name = file name without extension]

name: [package name]
version: [version number]
binaries-dsm: [binaries DSM name]
sources-dsm: [sources DSM name]
documentation-dsm: [documentation DSM name]
short-description: [One line of text]
long-description: [Multiple lines of text]
organisation: [e.g. FSF]
author:
author-email:
author-icq:
web-site: [Software's home page]
ftp-site:
porter:
porter-email:
porter-icq:
porting-web-site:
porting-ftp-site:
mailing-list:
mailing-list-administrator:
mailing-list-administrator-email:
mailing-list-administrator-icq:
mailing-list-web-site:
mailing-list-ftp-site:
newsgroup:
newsgroup-administrator:
newsgroup-administrator-email:
newsgroup-administrator-icq:
newsgroup-web-site:
newsgroup-ftp-site:

Installation & Dependencies
---------------------------

- The trailing slash on 'simtelnet-path' is optional.
- The file extension on 'zip' & 'tar-gzip' is required.

simtelnet-path: [e.g. v2tk/ - this is for auto-FTP or HTTP downloading]
zip: [File names in preferred order of installation]
zip-options:
tar-gzip: [File names in preferred order of installation]
tar-gzip-options:

pre-install-readme: [File name, extracted from zip/tgz]
post-install-readme: [File name]
pre-uninstall-readme: [File name]
post-uninstall-readme: [File name]

builtin-pre-install-script: [Built-in scripting]
builtin-post-install-script: [Built-in scripting]
builtin-pre-uninstall-script: [Built-in scripting]
builtin-post-uninstall-script: [Built-in scripting]

pre-install-script: [File name, extracted from zip/tgz]
post-install-script: [File name]
pre-uninstall-script: [File name]
post-uninstall-script: [File name]

prefix: [Directory off DJGPP root if zip not structured correctly]

- [Operator] can be any of the C operators  ==, <=, >=, !=, <, >.
  Optionally, we could allow '=' as an equality test. Omission of
  [Operator] implies an equality test.

- A package will automatically conflict with other versions of itself.

requires: [Package] [Operator] [Version]
depends-on: [Package] [Operator] [Version]
conflicts-with: [Package] [Operator] [Version]
replaces: [Packages] [Operator] [Version]
duplicate-action: [replace, backup-and-replace (or just 'backup'), keep,
                   skip, ask-user]

install-before: [Package] [Operator] [Version]
install-after: [Package] [Operator] [Version]
install-warning: [Message]

Notes
-----

- A group of packages has a DSM entry with a name such as "C development" and
  a list of 'requires' fields.

- The following directives were removed from the specification for version 0.2:
  . long-filename-script: [File name]
  . short-filename-script: [File name]

- The following directives were renamed between 0.1 and 0.2:
  . source -> sources-dsm

- Hashes should be used as comments. Blank lines should not, because these
  have special meaning in the package database. Sections of text should be
  separated by hashes.
--------------BA27717AF8B9EF54DE67E855--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019