From: "Joshua Brindle" <JBrindle@snu.edu>
To: <sds@epoch.ncsc.mil>, <selinux@tycho.nsa.gov>
Subject: Re: automake
Date: Tue, 03 Dec 2002 10:37:48 -0600 [thread overview]
Message-ID: <sdec8990.046@atlas.snu.edu> (raw)
Well, my distro will need the selinux-small archive _with_ the configure
system to compile correctly (obviously the ad hoc makefiles on the nsa
version won't do the job) so where will i get these from? or should i
just generate a patch and use it in conjunction with the nsa
distribution? IMO this really needs to be merged upstream, but if not
something needs to be done to make them available.
Joshua Brindle
UNIX Administrator
Southern Nazarene University
>>> "Stephen D. Smalley" <sds@epoch.ncsc.mil> 12/02/02 10:01AM >>>
> Are the patches to use automake with selinux going to be merged into
the
> selinux distribution on sourceforge?
If you are referring to the CVS repository at sourceforge, it mirrors
the public releases of SELinux from the NSA site. I wouldn't expect
the automake changes to be merged upstream in their current form,
since as far as I know, they only address selinux-small (not the full
set of SELinux-patched utilities and daemons) and are dependent on
the installation locations used by the Debian selinux package.
--
Stephen Smalley, NSA
sds@epoch.ncsc.mil
--
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 reply other threads:[~2002-12-03 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 16:37 Joshua Brindle [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-02 16:01 automake Stephen D. Smalley
2002-12-02 1:12 automake Joshua Brindle
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=sdec8990.046@atlas.snu.edu \
--to=jbrindle@snu.edu \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@tycho.nsa.gov \
/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.