mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de, Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [PATCH 4/5] sepolgen: remove after one year in staging
Date: Mon, 22 Jun 2020 14:56:36 +0200	[thread overview]
Message-ID: <20200622125636.GA129845@lenoch> (raw)
In-Reply-To: <20200622122644.GB23174@pengutronix.de>

On Mon, Jun 22, 2020 at 02:26:44PM +0200, Michael Olbrich wrote:
> On Mon, Jun 22, 2020 at 12:29:52AM +0200, Roland Hieber wrote:
> > Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> > ---
> >  rules/policycoreutils.in | 34 -------------------------
> >  rules/sepolgen.in        | 29 ---------------------
> >  rules/sepolgen.make      | 54 ----------------------------------------
> >  3 files changed, 117 deletions(-)
> >  delete mode 100644 rules/sepolgen.in
> >  delete mode 100644 rules/sepolgen.make
> > 
> > diff --git a/rules/policycoreutils.in b/rules/policycoreutils.in
> > index 856b50046d5b..27347b9f0188 100644
> > --- a/rules/policycoreutils.in
> > +++ b/rules/policycoreutils.in
> > @@ -11,7 +11,6 @@ menuconfig POLICYCOREUTILS
> >  	select LIBSEMANAGE
> >  	select LIBSEPOL
> >  	select DBUS_GLIB	if POLICYCOREUTILS_RESTORECOND
> > -	select SEPOLGEN		if POLICYCOREUTILS_PYTHON
> >  	select BUSYBOX_FEATURE_FIND_DEPTH	if BUSYBOX_FIND
> >  	select BUSYBOX_FEATURE_FIND_DELETE	if BUSYBOX_FIND
> >  	select BUSYBOX_SELINUX			if BUSYBOX_FIND
> > @@ -28,39 +27,6 @@ menuconfig POLICYCOREUTILS
> >  
> >  if POLICYCOREUTILS
> >  
> > -menuconfig POLICYCOREUTILS_PYTHON
> > -	depends on STAGING
> 
> Keep the options and replace STAGING with BROKEN and add a comment what's
> missing. The options are still referenced in the policycoreutils.make.

...and I have some selinux resurrection patches in progress, but
unfortunately customer stepped away from that requirement.

I'll try to find time to polish them and relase in case anybody
is in the mood of finishng that job ;-)

	ladis

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  reply	other threads:[~2020-06-22 12:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21 22:29 [ptxdist] [PATCH 1/5] ustr: move to staging Roland Hieber
2020-06-21 22:29 ` [ptxdist] [PATCH 2/5] dc3dd: remove after one year in staging Roland Hieber
2020-06-26 11:00   ` [ptxdist] [APPLIED] " Michael Olbrich
2020-06-21 22:29 ` [ptxdist] [PATCH 3/5] mono: " Roland Hieber
2020-06-26 11:00   ` [ptxdist] [APPLIED] " Michael Olbrich
2020-06-21 22:29 ` [ptxdist] [PATCH 4/5] sepolgen: " Roland Hieber
2020-06-22 12:26   ` Michael Olbrich
2020-06-22 12:56     ` Ladislav Michl [this message]
2020-06-28 21:20     ` [ptxdist] [PATCH v2] " Roland Hieber
2020-06-28 21:24     ` [ptxdist] [PATCH v3] " Roland Hieber
2020-07-06  6:38       ` Michael Olbrich
2020-07-06 12:49         ` [ptxdist] [PATCH v2] " Roland Hieber
2020-07-07  5:45           ` [ptxdist] [APPLIED] " Michael Olbrich
2020-06-21 22:29 ` [ptxdist] [PATCH 5/5] udisks: " Roland Hieber
2020-06-26 11:00   ` [ptxdist] [APPLIED] " Michael Olbrich
2020-06-26 11:00 ` [ptxdist] [APPLIED] ustr: move to staging Michael Olbrich

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=20200622125636.GA129845@lenoch \
    --to=ladis@linux-mips.org \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox