All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Joshua Brindle <method@manicmethod.com>,
	selinux@tycho.nsa.gov, Darrel Goeddel <dgoeddel@TrustedCS.com>
Subject: Re: [PATCH 0/6] Drop legacy boolean/users support (setlocaldefs)
Date: Thu, 26 Apr 2007 12:28:21 -0400	[thread overview]
Message-ID: <1177604901.3405.13.camel@localhost.localdomain> (raw)
In-Reply-To: <1177601905.24282.354.camel@moss-spartans.epoch.ncsc.mil>

On Thu, 2007-04-26 at 11:38 -0400, Stephen Smalley wrote:
> On Thu, 2007-04-26 at 11:28 -0400, Joshua Brindle wrote:
> > Stephen Smalley wrote:
> > > The following patch series completely removes the legacy support for
> > > local boolean and user definitions (setlocaldefs) from libsepol and
> > > libselinux and updates libsemanage and policycoreutils for the resulting
> > > interface changes and removals.  As such, it requires bumping the .so
> > > versions, which has already been done on the policyrep branch (and these
> > > patches are therefore intended to be applied there first, and then
> > > merged to trunk later along with the policyrep work).
> > >
> > >   
> > Hrm, it doesn't seem appropriate to merge things entirely unrelated to 
> > the policyrep branch into that branch just because the soversion was 
> > bumped there. Karl, what do you think about this?
> 
> The alternative is to apply it in a separate branch and merge them
> separately to trunk or merge them together later and then to trunk.
> Seems less painful to get it all done together, only bump the .so
> version once, and avoid conflicts a priori by keeping it within a single
> devel branch.
> 
> So, at worst, the branch is ill-named ;)
> 

I'm fine with mixing them - I thought that the plan from the beginning
was to break compatibility once.

Karl


--
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.

  reply	other threads:[~2007-04-26 16:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 13:40 [PATCH 0/6] Drop legacy boolean/users support (setlocaldefs) Stephen Smalley
2007-04-26 13:45 ` [PATCH 1/6] libselinux: Drop setlocaldefs support from policy loading code Stephen Smalley
2007-04-26 13:51 ` [PATCH 2/6] libsepol: Remove obsolete interfaces and code used to support local boolean and user files Stephen Smalley
2007-04-26 13:53 ` [PATCH 3/6] libselinux: Remove obsolete interfaces and code for " Stephen Smalley
2007-04-26 13:55 ` [PATCH 4/6] libsemanage: update for interface change to libselinux Stephen Smalley
2007-04-26 13:56 ` [PATCH 5/6] audit2why: update for interface change to libsepol Stephen Smalley
2007-04-26 13:57 ` [PATCH 6/6] setsebool: Update for interface change to libselinux Stephen Smalley
2007-04-26 15:28 ` [PATCH 0/6] Drop legacy boolean/users support (setlocaldefs) Joshua Brindle
2007-04-26 15:38   ` Stephen Smalley
2007-04-26 16:28     ` Karl MacMillan [this message]
2007-04-26 18:48 ` Karl MacMillan

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=1177604901.3405.13.camel@localhost.localdomain \
    --to=kmacmillan@mentalrootkit.com \
    --cc=dgoeddel@TrustedCS.com \
    --cc=method@manicmethod.com \
    --cc=sds@tycho.nsa.gov \
    --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.