All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] PyXML requirement for refpolicy
Date: Fri, 31 Oct 2014 10:21:22 -0400	[thread overview]
Message-ID: <54539AE2.8000401@tresys.com> (raw)
In-Reply-To: <CAJfZ7=m4i-7rnhicZ+y=UfdKYXH4eH7DwbsXyTt=jTKZKWvzAg@mail.gmail.com>

On 10/30/2014 6:05 PM, Nicolas Iooss wrote:
> Refpolicy INSTALL file says that PyXML is required for building [1].
> However I haven't got this library on my system and things are working
> well so I'm wondering what I am missing. A simple "git grep import"
> shows "from xml.dom.minidom import parse, parseString" in
> support/sedoctool.py [2] but the xml module has been part of Python
> since Python 2.0 (according to 2.6 doc [3]) so this is not PyXML.
> Moreover PyXML main page says this library is no longer maintained [4].
> 
> Is PyXML still a requirement of refpolicy and if not, is it possible to
> remove it from the INSTALL file?

I believe you are correct that it can be removed.  These things should
work, to verify:

* 'make conf' will yield doc/policy.xml, which will validate against
doc/policy.dtd. The makefile already validates, so this checks out.
* doc/policy.xml should have all of the xml docs from throughout the policy
* 'make html' should get all the html interface docs

If that all works, then we can update the INSTALL and other
documentation to replace PyXML with Python 2.0 in the dependency list.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  reply	other threads:[~2014-10-31 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 22:05 [refpolicy] PyXML requirement for refpolicy Nicolas Iooss
2014-10-31 14:21 ` Christopher J. PeBenito [this message]
2014-11-03 20:14   ` Nicolas Iooss
2014-11-04 12:59     ` Christopher J. PeBenito

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=54539AE2.8000401@tresys.com \
    --to=cpebenito@tresys.com \
    --cc=refpolicy@oss.tresys.com \
    /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.