From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net
Cc: Mark Ver <markver@us.ibm.com>
Subject: Re: [LTP] older distribution levels
Date: Mon, 31 Aug 2009 18:31:22 -0400 [thread overview]
Message-ID: <200908311831.23233.vapier@gentoo.org> (raw)
In-Reply-To: <OF78939903.9E28133E-ON85257623.00782F9F-85257623.007A366B@us.ibm.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 578 bytes --]
On Monday 31 August 2009 18:14:52 Mark Ver wrote:
> 1) new testcases expect new features and don't properly address compiling
> and/or running on the kernel and subsystems provided on the older
> distribution.
there is already a standard: add autoconf tests
> 2) the LTP build itself requires new software (mostly new versions of
> autoconf) which are not yet provided on the older distribution.
if you're doing development, upgrade your distro. older distros should be
given an ltp with autotools already generated (like happens with ltp
releases).
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 355 bytes --]
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2009-08-31 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 22:14 [LTP] older distribution levels Mark Ver
2009-08-31 22:31 ` Mike Frysinger [this message]
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=200908311831.23233.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=markver@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox