From: Daniel J Walsh <dwalsh@redhat.com>
To: SELinux <SELinux@tycho.nsa.gov>
Subject: Broke libselinux into two packages
Date: Thu, 09 Oct 2003 09:01:41 -0400 [thread overview]
Message-ID: <3F855C35.9060508@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
It was pointed out to me that their should be two packages for
libselinux. Basically the shared libraries and a devel rpm containing .a and .h files.
Packages are out on ftp://people.redhat.com/dwalsh/SELinux/Fedora
Dan
[-- Attachment #2: Re: Broke libselinux into two packages. --]
[-- Type: message/rfc822, Size: 1889 bytes --]
From: Stephen Smalley <sds@epoch.ncsc.mil>
To: Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: Broke libselinux into two packages.
Date: 09 Oct 2003 08:55:31 -0400
Message-ID: <1065704131.8181.181.camel@moss-spartans.epoch.ncsc.mil>
On Thu, 2003-10-09 at 08:53, Daniel J Walsh wrote:
> It was pointed out to me that their should be two packages for
> libselinux. Basically the
> shared libraries and a devel rpm containing .a and .h files.
>
> Packages are out on people.
You should send this kind of email (along with your earlier patch) to
the public selinux list. Why not?
--
Stephen Smalley <sds@epoch.ncsc.mil>
National Security Agency
reply other threads:[~2003-10-09 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F855C35.9060508@redhat.com \
--to=dwalsh@redhat.com \
--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.