/ Peter Ring <[EMAIL PROTECTED]> was heard to say:
| And now that we are at it, what would be the preferred way to mark up the
| dependencies between packages and other resources in a computable way, i.e.,
| in a way that could be derived from a package description, or, even better,
| could generate a package description?
If I was doing this, I'd design a vocabulary just for this purpose.
Something concise and tailored to the task. I'd generate DocBook from
that format for documentation.
Be seeing you,
norm
--
Norman Walsh <[EMAIL PROTECTED]> | Anything more than the truth would
http://www.oasis-open.org/docbook/ | be too much.--Robert Frost
Chair, DocBook Technical Committee |
------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: [EMAIL PROTECTED]
- DOCBOOK: tagging package names (rpm, deb) Mark Johnson
- Re: DOCBOOK: tagging package names (rpm, deb) David Mason
- Re: DOCBOOK: tagging package names (rpm, deb) Mark Johnson
- Re: DOCBOOK: tagging package names (rpm, deb) David Mason
- DOCBOOK: Re: tagging package names (rpm, deb) Karl Eichwalder
- RE: DOCBOOK: tagging package names (rpm, deb) Peter Ring
- Re: DOCBOOK: tagging package names (rpm, deb) Norman Walsh
- Re: DOCBOOK: tagging package names (rpm, deb) David Johnson
- Re: DOCBOOK: tagging package names (rpm, deb) Norman Walsh
- Re: DOCBOOK: tagging package names (rpm, deb) Nik Clayton
- Re: DOCBOOK: tagging package names (rpm, deb) Nik Clayton
- Re: DOCBOOK: tagging package names (rpm, deb) Norman Walsh
- Re: DOCBOOK: tagging package names (rpm, deb) Mark Johnson
- Re: DOCBOOK: tagging package names (rpm, deb) Norman Walsh
