From: "gndeva@ispwest.com" <gndeva@ispwest.com>
To: "John D. Ramsdell" <ramsdell@mitre.org>
Cc: Karl MacMillan <kmacmillan@tresys.com>,
SELinux List <SELinux@tycho.nsa.gov>
Subject: Re: GNU Coding Standards
Date: Fri, 14 Nov 2003 10:23:55 -0800 [thread overview]
Message-ID: <3FB51DBB.7070308@ispwest.com> (raw)
In-Reply-To: <ogtn0az2dqq.fsf@divan.mitre.org>
Note that GNU automake requires perl, which does
not seem to be in the base selinux tool chest
(at least in the 2.4 flavor).
In making test systems from scratch I've been
finding these chicken-egg problems with the
tool chain. I've been considering using
the busybox package as a bootstrap mechanism.
John D. Ramsdell wrote:
> Karl MacMillan <kmacmillan@tresys.com> writes:
>
>
>>We have just released version 1.0.1 of setools.
>
>
> ...
>
>
>>The next release, sometime in early December, will include improved
>>information flow analysis, the ability to save and load complex
>>queries in apol, the removal of Tcl/TK and X dependencies from the
>>command-line tools, and a log file analysis tool that leverages
>>libapol to help a policy developer or system administrator
>>understand the audit message from SELinux.
>
>
> Karl,
>
> It would also be very helpful if the setools distribution adhered to
> GNU Coding Standards. The standards have been developed over a long
> period of time, and compliant distributions fit into the Linux
> framework well. Furthermore, tools are available that automate most
> of the work needed to meet the standards. The lastest generation of
> autoconf, automake, libtool, and autoheader, make managing releases a
> no-brainer.
>
> If you're not an Emacs user, you can read about the GNU Coding
> Standards with the command "info standards".
>
> You can see an example of a distribution that meets the standards in
> the selinux-usr/slat directory of the nsa module in the selinux
> project's CVS repository on SourceForge. I just finished tuning it.
>
> John
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.
>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2003-11-14 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 20:16 Setools 1.0.1 released Karl MacMillan
2003-11-04 0:54 ` GDM and PAM problems? Richard Herbert Wanner
2003-11-04 4:13 ` Daniel J Walsh
2003-11-04 13:46 ` Setools 1.0.1 released Karl MacMillan
2003-11-07 13:15 ` Dale Amon
2003-11-07 16:21 ` Karl MacMillan
2003-11-07 21:23 ` Dale Amon
2003-11-14 15:04 ` GNU Coding Standards (was: Setools 1.0.1 released) John D. Ramsdell
2003-11-14 17:03 ` Karl MacMillan
2003-11-14 18:23 ` gndeva [this message]
2003-11-14 21:48 ` GNU Coding Standards Russell Coker
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=3FB51DBB.7070308@ispwest.com \
--to=gndeva@ispwest.com \
--cc=SELinux@tycho.nsa.gov \
--cc=kmacmillan@tresys.com \
--cc=ramsdell@mitre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.