public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: ltp-list <ltp-list@lists.sf.net>
Subject: Re: [LTP] selinux-testsuite has moved
Date: Mon, 25 Apr 2011 16:20:21 -0300	[thread overview]
Message-ID: <1303759223.2325.11.camel@freedom> (raw)
In-Reply-To: <1303738356.4244.67.camel@moss-pluto>

On Mon, 2011-04-25 at 09:32 -0400, Stephen Smalley wrote:

> At present we see no benefit, only cost, to maintaining the selinux
> testsuite in the ltp as it is regularly broken by unrelated changes
> elsewhere in the ltp and as it is not truly integrated into the ltp (you
> have to perform separate steps to build and run it).  In comparison, we
> don't have to worry about unrelated changes breaking the standalone
> selinux testsuite, and it is certainly no harder to do this:
> 
> git clone git://git.kernel.org/pub/scm/tests/selinux-testsuite
> cd selinux-testsuite
> sudo make test
> 
> than to do this:
> 
> git clone git://ltp.git.sourceforge.net/gitroot/ltp/ltp
> cd ltp
> make autotools
> ./configure
> make all
> make install
> cd testcases/kernel/security/selinux-testsuite
> make all
> make install
> cd /opt/ltp
> ./testscripts/test_selinux.sh
> 
> If the selinux testsuite were fully integrated into the ltp (e.g. built
> and run by default if SELinux is enabled on the system), then that might
> be more worthwhile to keep it as part of the ltp.  But in the 6 years
> since it was added to the ltp, that hasn't happened. 

+1 for this. In the end of the day, what matters for a software project
is maintenance. Since we have a working, maintained git repo with the
selinux testsuite, it's better than having it half integrated with LTP,
so the better choice here IMHO is to just remove it from the LTP tree.

I know LTP aims to be comprehensive, but this comprehensiveness has to
be achieved through tightly integrated code, no point in keeping
disconnected pieces of code in the tree, that will likely break and
bitrot. I wish I could commit in looking at all current testsuites
merged into LTP that need better integration so we can opt by:

1) Remove
2) Do what it takes to get it fully integrated in terms of API, build
system, workflow.

I am not an LTP maintainer so I feel like I'm meddling on other people's
business, however I thought it'd be worth to point this out... take it
with a grain of salt.

Cheers,

Lucas


------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2011-04-25 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-22 13:08 [LTP] selinux-testsuite has moved Stephen Smalley
2011-04-22 20:43 ` Shubham Goyal
2011-04-25 13:32   ` Stephen Smalley
2011-04-25 19:20     ` Lucas Meneghel Rodrigues [this message]
2011-04-25 19:38     ` Garrett Cooper
2011-04-26 13:21       ` Stephen Smalley
2011-05-06 11:25         ` Cyril Hrubis
     [not found]           ` <1304686654.1821.14.camel@moss-pluto>
2011-05-11 12:39             ` Cyril Hrubis
2012-01-17  9:48 ` Jan Stancek
2012-01-18 13:16   ` Cyril Hrubis

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=1303759223.2325.11.camel@freedom \
    --to=lmr@redhat.com \
    --cc=ltp-list@lists.sf.net \
    --cc=sds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox