From: Scott James Remnant <scott@netsplit.com>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: SE-Linux <selinux@tycho.nsa.gov>,
Dpkg Development <debian-dpkg@lists.debian.org>,
Debian Developers <debian-devel@lists.debian.org>
Subject: Re: dpkg and selinux
Date: Wed, 01 Sep 2004 21:50:28 +0100 [thread overview]
Message-ID: <1094071829.6901.149.camel@descent.netsplit.com> (raw)
In-Reply-To: <20040901172551.GC4400@lkcl.net>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
On Wed, 2004-09-01 at 18:25 +0100, Luke Kenneth Casson Leighton wrote:
> On Wed, Sep 01, 2004 at 02:30:03PM +0100, Scott James Remnant wrote:
> > However I'm loath to embed specific selinux support into dpkg if it
> > introduces extra dependencies, or causes problems for those not using
> > it.
>
> 1) fortunately, the only extra dependency will be libselinux1 which
> needs to be made "Required" such that cron, coreutils, logrotate,
> ssh etc. can use it.
>
That rules that solution out, then. I'm not going to add a dpkg
dependency on libselinux until selinux is the default (over chown/chmod/
etc.)
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-01 20:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 23:41 dpkg and selinux Luke Kenneth Casson Leighton
2004-09-01 2:12 ` Scott James Remnant
2004-09-01 10:19 ` Luke Kenneth Casson Leighton
2004-09-01 13:30 ` Scott James Remnant
2004-09-01 17:25 ` Luke Kenneth Casson Leighton
2004-09-01 20:50 ` Scott James Remnant [this message]
2004-09-01 21:32 ` Luke Kenneth Casson Leighton
2004-09-01 22:29 ` Scott James Remnant
2004-09-07 12:20 ` Russell Coker
2004-09-07 12:39 ` Luke Kenneth Casson Leighton
2004-09-08 13:32 ` Russell Coker
2004-09-08 22:02 ` Luke Kenneth Casson Leighton
2004-09-07 12:25 ` Russell Coker
2004-09-01 17:47 ` Luke Kenneth Casson Leighton
2004-09-07 12:13 ` 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=1094071829.6901.149.camel@descent.netsplit.com \
--to=scott@netsplit.com \
--cc=debian-devel@lists.debian.org \
--cc=debian-dpkg@lists.debian.org \
--cc=lkcl@lkcl.net \
--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.