From: Jim Kingdon <kingdon@redhat.com>
To: elix@sourceware.cygnus.com
Cc: lsb-spec@lists.linuxbase.org
Subject: Cooperation between EL/IX and LSB
Date: Thu, 27 Jan 2000 10:48:00 -0000 [thread overview]
Message-ID: <200001271848.NAA02772@devserv.devel.redhat.com> (raw)
In the Linux Standard Base (LSB) we have often wished there were a bit
more coordination between EL/IX and the LSB
( http://www.linuxbase.org/ ) since after all the EL/IX level 4 API is
probably pretty much synonymous with the LSB API (the efforts are not
quite the same, for one thing the LSB also is working on an ABI,
anyway, the point is there is overlap not that we're identical).
Here's what I have done so far:
* Added link from http://www.linuxbase.org/links.html to EL/IX.
Here's what we can do:
* If EL/IX would be interested in adding a link from the EL/IX web
site to linuxbase.org, that would be great.
* Linuxbase.org is currently a distributed (that is, support from many
vendors) effort that maintains our specification via CVS - see
http://www.linuxbase.org/devel.html
We would like to ask whether EL/IX would be interested in
maintaining the EL/IX specification in the same way. In particular,
the LSB spec is maintained in a combination of
MySQL/DocBook/makefiles which, although somewhat complicated, makes
it easy to add additional columns for "included in EL/IX level 1"?
"included in EL/IX level 2"? And so on. It already has columns for
Single Unix Spec, POSIX, &c.
You should be able to check out the files read-only from CVS if you
want to play with this - if maintaining the specs together seems
like a good plan we should be able to arrange for EL/IX people to
have write access as well.
* Any other ideas? Let us know. I've CC'd this message between the
mailing lists of the two projects.
next reply other threads:[~2000-01-27 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-27 10:48 Jim Kingdon [this message]
2000-01-29 13:07 ` Paul Beskeen
2000-01-29 20:36 ` Jim Kingdon
2000-01-30 8:20 ` Stuart Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200001271848.NAA02772@devserv.devel.redhat.com \
--to=kingdon@redhat.com \
--cc=elix@sourceware.cygnus.com \
--cc=lsb-spec@lists.linuxbase.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).